# CVE-2012-2389: Information disclosure in n/a

> Local attackers can read sensitive credentials from the hostapd configuration file due to insecure file permissions.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-g3f4-94xv-v6fv

## What is CVE-2012-2389?

CVE-2012-2389 is a low-severity vulnerability in n/a, published on 21 Jun 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

hostapd 0.7.3, and possibly other versions before 1.0, uses 0644 permissions for /etc/hostapd/hostapd.conf, which might allow local users to obtain sensitive information such as credentials.

Weakness: CWE-264

## Which versions are affected by CVE-2012-2389?

It affects 1 product.


Products: W1.fi Hostapd.

## How do I fix CVE-2012-2389?

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

## Is CVE-2012-2389 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10743](https://insights.sbomify.com/CVE-2016-10743/): Weak cryptography in n/a (high 7.5)
- [CVE-2019-5061](https://insights.sbomify.com/CVE-2019-5061/): Denial of service in W1.f1 (high 7.4)
- [CVE-2019-5062](https://insights.sbomify.com/CVE-2019-5062/): Denial of service in W1.f1 (high 7.4)
- [CVE-2026-58374](https://insights.sbomify.com/CVE-2026-58374/): Memory corruption in hostapd (medium 6.5)
- [CVE-2022-37660](https://insights.sbomify.com/CVE-2022-37660/): Other in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2389 and fix it if it is affected.

What it is: CVE-2012-2389 is a low-severity vulnerability in n/a, published on 21 Jun 2012. 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-2012-2389 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-2012-2389/ (Markdown: https://insights.sbomify.com/CVE-2012-2389/index.md)
```

## Sources

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

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