# CVE-2006-2229: Information disclosure in n/a

> Remote attackers can view sensitive information or cause denial of service if OpenVPN's management interface is exposed on a non-loopback IP with cleartext passwords.

- **Severity:** Medium 4.0 (`AV:N/AC:H/Au:N/C:P/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q6wh-cc86-fx6h

## What is CVE-2006-2229?

CVE-2006-2229 is a medium-severity vulnerability in n/a, published on 5 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenVPN 2.0.7 and earlier, when configured to use the --management option with an IP that is not 127.0.0.1, uses a cleartext password for TCP sessions to the management interface, which might allow remote attackers to view sensitive information or cause a denial of service.

## Which versions are affected by CVE-2006-2229?

It affects 2 products.


Products: Openvpn Openvpn, Openvpn Openvpn Access Server.

## How do I fix CVE-2006-2229?

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

## Is CVE-2006-2229 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-12106](https://insights.sbomify.com/CVE-2025-12106/): Memory corruption in OpenVPN (critical 9.1)
- [CVE-2024-5594](https://insights.sbomify.com/CVE-2024-5594/): Information disclosure in OpenVPN (critical 9.1)
- [CVE-2018-7544](https://insights.sbomify.com/CVE-2018-7544/): Cross-site request forgery in n/a (critical 9.1)
- [CVE-2006-1629](https://insights.sbomify.com/CVE-2006-1629/): Code injection in n/a (critical 9.0)
- [CVE-2024-4877](https://insights.sbomify.com/CVE-2024-4877/): Privilege escalation in OpenVPN (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2229 and fix it if it is affected.

What it is: CVE-2006-2229 is a medium-severity vulnerability in n/a, published on 5 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2229 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-2006-2229/ (Markdown: https://insights.sbomify.com/CVE-2006-2229/index.md)
```

## Sources

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

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