# CVE-2014-0241: rubygem-hammer_cli_foreman: File /etc/hammer/cli.modules.d/foreman.yml world readable


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 13 Dec 2019
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-h459-7mrx-8pvc

## What is CVE-2014-0241?

CVE-2014-0241 is a medium-severity vulnerability in Redhat Satellite, published on 13 Dec 2019. 

### Official description

rubygem-hammer_cli_foreman: File /etc/hammer/cli.modules.d/foreman.yml world readable

Weakness: CWE-522 (Insufficiently Protected Credentials)

## Which versions are affected by CVE-2014-0241?

It affects 2 products.


Products: Redhat Satellite, Theforeman Hammer Cli.

## How do I fix CVE-2014-0241?

Upgrade to a fixed version.

## Is CVE-2014-0241 being exploited?

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

## Other vulnerabilities in Redhat Satellite

- [CVE-2024-7012](https://insights.sbomify.com/CVE-2024-7012/): Puppet-foreman: an authentication bypass vulnerability exists in foreman (critical 9.8)
- [CVE-2024-7923](https://insights.sbomify.com/CVE-2024-7923/): Puppet-pulpcore: an authentication bypass vulnerability exists in pulpcore (critical 9.8)
- [CVE-2026-96659](https://insights.sbomify.com/CVE-2026-96659/): Foreman: excessive permissions for viewer role on preview (critical 9.1)
- [CVE-2023-0118](https://insights.sbomify.com/CVE-2023-0118/): Foreman: arbitrary code execution through templates (critical 9.1)
- [CVE-2008-2369](https://insights.sbomify.com/CVE-2008-2369/): Hardcoded credentials in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0241 and fix it if it is affected.

What it is: CVE-2014-0241 is a medium-severity vulnerability in Redhat Satellite, published on 13 Dec 2019. 
Exploitation: There is no known exploitation of CVE-2014-0241 in the wild and no public exploit code.

Affected product: Redhat Satellite. 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-2014-0241/ (Markdown: https://insights.sbomify.com/CVE-2014-0241/index.md)
```

## Sources

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

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