Local vulnerability in WeFi Client v3.

2008-07-06 / 2008-07-07
Credit: Xia Shing Zee
Risk: Medium
Local: Yes
Remote: No
CWE: CWE-200

CVSS Base Score: 4.7/10
Impact Subscore: 6.9/10
Exploitability Subscore: 3.4/10
Exploit range: Local
Attack complexity: Medium
Authentication: No required
Confidentiality impact: Complete
Integrity impact: None
Availability impact: None

================================================== INFO ================================================== The wireless client, WeFi v3. 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_at_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



Vote for this issue:


Thanks for you vote!


Thanks for you comment!
Your message is in quarantine 48 hours.

Comment it here.

(*) - required fields.  
{{ x.nick }} | Date: {{ x.ux * 1000 | date:'yyyy-MM-dd' }} {{ x.ux * 1000 | date:'HH:mm' }} CET+1
{{ x.comment }}

Copyright 2020, cxsecurity.com


Back to Top