# CVE-2009-5066: Information disclosure in n/a

> Local attackers can read JBoss credentials by inspecting process arguments, exposing sensitive authentication data.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/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:** Yes
- **Published:** 13 Aug 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2g9h-3ggp-8xg3

## What is CVE-2009-5066?

CVE-2009-5066 is a low-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 13 Aug 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

twiddle.sh in JBoss AS 5.0 and EAP 5.0 and earlier accepts credentials as command-line arguments, which allows local users to read the credentials by listing the process and its arguments.

Weakness: CWE-255

## Which versions are affected by CVE-2009-5066?

It affects 2 products.


Products: Redhat Jboss Community Application Server, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2009-5066?

Apply the vendor's patch.

## Is CVE-2009-5066 being exploited?

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

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2012-4529](https://insights.sbomify.com/CVE-2012-4529/): Information disclosure in n/a (medium 4.3)
- [CVE-2012-2148](https://insights.sbomify.com/CVE-2012-2148/): Security feature bypass in AS (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-5066 and fix it if it is affected.

What it is: CVE-2009-5066 is a low-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 13 Aug 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-2009-5066 in the wild and no public exploit code.

Affected product: Redhat Jboss Enterprise Application Platform. 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-2009-5066/ (Markdown: https://insights.sbomify.com/CVE-2009-5066/index.md)
```

## Sources

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

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