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

> Local attackers can read credentials from a world-readable temporary file in the Aeolus Configuration Server setup.

- **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:** 12 Mar 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4m29-g7f4-9v6x

## What is CVE-2012-5509?

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

### Official description

aeolus-configserver-setup in the Aeolas Configuration Server, as used in Red Hat CloudForms Cloud Engine before 1.1.2, uses world-readable permissions for a temporary file in /tmp, which allows local users to read credentials by reading this file.

Weakness: CWE-264

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

It affects 1 product.


Products: Redhat Cloudforms Cloud Engine.

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

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

## Is CVE-2012-5509 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-6117](https://insights.sbomify.com/CVE-2012-6117/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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