what you don't know can hurt you

wefi-local.txt

wefi-local.txt
Posted Jul 10, 2008
Authored by Xia Shing Zee

The wireless client, WeFi version 3.2.1.4.1, is susceptible to local vulnerabilities due to improper coding.

tags | advisory, local, vulnerability
MD5 | 9e018650561ebf7a0b390aa09e01bb54

wefi-local.txt

Change Mirror Download
==================================================
INFO
==================================================
The wireless client, WeFi v3.2.1.4.1 is susceptible to local vulnerabilities due to improper coding. Earlier versions may

also be affected.

==================================================
DISCUSSION
==================================================
Due to lack of improper encryption and the client storing backups of the log files, a local attacker can gain unencrypted keys to WEP, WPA and WPA2 access points. The log files that keep the keys are as follows:

C:\Program Files\WeFi\LogFiles\ClientWeFiLog.dat
C:\Program Files\WeFi\LogFiles\ClientWeFiLog.bak
C:\Program Files\WeFi\Users\mee@sheep.com.inf (Yet to be confirmed, heavily encrypted)

==================================================
SAMPLE
==================================================
Here is a sample of the backup file code:
a11ae90c2b66|7a000b|6|c8e|736|3f2a|ffffffff|0|0|35|6570|Create Profile|
a11ae90c2d4a|7a000b|6|c8e|736|3f2a|ffffffff|0|0|35|6571|try to connect|
a11ae90c2d4a|7a000b|6|c8e|736|3f2a|ffffffff|0|0|35|6572|09F82980CX|

As you can see, the key has been stored in plain text at the end of the last line.

==================================================
NOTES
==================================================
It is to be noted that the backup file, .bak, is still viewable even after the client is closed. When the .dat file exceeds 3000kb, it moves the data to the .bak file and subsequently when that file exceeds 3000kb, the data is deleted. This can exceed over a day of normal internet browsing.

The .dat file shows the unencrypted keys several lines after the phrase, "Create Profile". It also shows failed attempts at connecting to a wireless access point.

==================================================
SOLUTION
==================================================
Use heavier encryption or do not keep log files.
The vendor has been notified.

==================================================
Thanks,
Xia Shing Zee
Login or Register to add favorites

File Archive:

July 2020

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Jul 1st
    13 Files
  • 2
    Jul 2nd
    0 Files
  • 3
    Jul 3rd
    0 Files
  • 4
    Jul 4th
    0 Files
  • 5
    Jul 5th
    0 Files
  • 6
    Jul 6th
    0 Files
  • 7
    Jul 7th
    0 Files
  • 8
    Jul 8th
    0 Files
  • 9
    Jul 9th
    0 Files
  • 10
    Jul 10th
    0 Files
  • 11
    Jul 11th
    0 Files
  • 12
    Jul 12th
    0 Files
  • 13
    Jul 13th
    0 Files
  • 14
    Jul 14th
    0 Files
  • 15
    Jul 15th
    0 Files
  • 16
    Jul 16th
    0 Files
  • 17
    Jul 17th
    0 Files
  • 18
    Jul 18th
    0 Files
  • 19
    Jul 19th
    0 Files
  • 20
    Jul 20th
    0 Files
  • 21
    Jul 21st
    0 Files
  • 22
    Jul 22nd
    0 Files
  • 23
    Jul 23rd
    0 Files
  • 24
    Jul 24th
    0 Files
  • 25
    Jul 25th
    0 Files
  • 26
    Jul 26th
    0 Files
  • 27
    Jul 27th
    0 Files
  • 28
    Jul 28th
    0 Files
  • 29
    Jul 29th
    0 Files
  • 30
    Jul 30th
    0 Files
  • 31
    Jul 31st
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2020 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close