# CVE-2008-3147: Information disclosure in n/a

> Local attackers can read cleartext Wi-Fi keys from log files when diagnostic mode is enabled in WeFi.

- **Severity:** Medium 4.7 (`AV:L/AC:M/Au:N/C:C/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x826-r76q-3v66

## What is CVE-2008-3147?

CVE-2008-3147 is a medium-severity vulnerability in n/a, published on 11 Jul 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WeFi 3.2.1.4.1, when diagnostic mode is enabled, stores (1) WEP, (2) WPA, and (3) WPA2 access-point keys in (a) ClientWeFiLog.dat, (b) ClientWeFiLog.bak, and possibly (c) a certain .inf file under %PROGRAMFILES%\WeFi\Users\, and uses cleartext for the ClientWeFiLog files, which allows local users to obtain sensitive information by reading these files.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2008-3147?

It affects 1 product.


Products: Wefi Wefi.

## How do I fix CVE-2008-3147?

No fix has been published for CVE-2008-3147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2008-3147 being exploited?

There is no known exploitation of CVE-2008-3147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3147 and fix it if it is affected.

What it is: CVE-2008-3147 is a medium-severity vulnerability in n/a, published on 11 Jul 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2008-3147 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2008-3147/ (Markdown: https://insights.sbomify.com/CVE-2008-3147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2008-3147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2008-3147
- OSV: https://osv.dev/vulnerability/CVE-2008-3147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2008-3147/
Summaries are generated and may contain mistakes; the official description above is the record.