# CVE-2012-5477: Misconfiguration in n/a

> Local attackers can modify files created by the Foreman smart proxy daemon due to an insecure umask setting.

- **Severity:** Low 3.6 (`AV:L/AC:L/Au:N/C:N/I:P/A:P`)
- **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:** 8 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9crx-xc3m-v3x2

## What is CVE-2012-5477?

CVE-2012-5477 is a low-severity vulnerability in Theforeman Foreman, published on 8 May 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The smart proxy in Foreman before 1.1 uses a umask set to 0, which allows local users to modify files created by the daemon via unspecified vectors.

Weakness: CWE-264

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

It affects 1 product.


Products: Theforeman Foreman.

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

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

## Is CVE-2012-5477 being exploited?

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

## Other vulnerabilities in Theforeman Foreman

- [CVE-2018-14643](https://insights.sbomify.com/CVE-2018-14643/): smart_proxy_dynflow gem authentication bypass in Foreman remote execution feature (critical 9.8)
- [CVE-2017-7505](https://insights.sbomify.com/CVE-2017-7505/): Missing authorization in foreman (high 8.8)
- [CVE-2016-4475](https://insights.sbomify.com/CVE-2016-4475/): Missing authorization in n/a (high 8.8)
- [CVE-2016-3728](https://insights.sbomify.com/CVE-2016-3728/): Code injection in n/a (high 8.8)
- [CVE-2015-5246](https://insights.sbomify.com/CVE-2015-5246/): Auth bypass in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5477 is a low-severity vulnerability in Theforeman Foreman, published on 8 May 2014. 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-5477 in the wild and no public exploit code.

Affected product: Theforeman Foreman. 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-5477/ (Markdown: https://insights.sbomify.com/CVE-2012-5477/index.md)
```

## Sources

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

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