dbcve.org
SatelliteApplication · Redhat

CVE-2014-0241

MEDIUM · 5.5 CVSS v3.1 Published 2019-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The rubygem-hammer_cli_foreman package stores configuration in /etc/hammer/cli.modules.d/foreman.yml with world-readable permissions (0644), allowing any local user on the system to read potentially sensitive configuration data.

MitigationChange the file permissions on /etc/hammer/cli.modules.d/foreman.yml to restrict read access (e.g., chmod 600 or chmod 640) and verify the hammer CLI tool functions correctly after the change.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SatelliteApplication
Affected:= 6.0
Hammer CliApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the foreman.yml configuration file
    Check if the file /etc/hammer/cli.modules.d/foreman.yml exists on the system using: ls -la /etc/hammer/cli.modules.d/foreman.yml
    Affected if The file does not exist (not vulnerable because there is no configuration to read)
  2. Inspect file permissions on foreman.yml
    Run: stat -c '%a' /etc/hammer/cli.modules.d/foreman.yml to get the octal permission bits
    Affected if The permission bits are 0644 or otherwise allow world read access (e.g., 0644, 0647, 0655)
  3. Verify world-readable status
    Run: ls -l /etc/hammer/cli.modules.d/foreman.yml and check if the 'others' column shows 'r--' or 'r-x' permissions
    Affected if The file shows read permission for 'others' or 'world' (last three characters are 'r--' or similar)
  4. Confirm hammer_cli_foreman package is installed
    Run: rpm -q rubygem-hammer_cli_foreman or check via your package manager if the package is present
    Affected if The package is installed AND the config file has world-readable permissions

A user is affected if the /etc/hammer/cli.modules.d/foreman.yml file exists with 0644 or equivalent world-readable permissions, allowing any local user to read potentially sensitive configuration data.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Change the file permissions on /etc/hammer/cli.modules.d/foreman.yml to restrict read access (e.g., chmod 600 or chmod 640) and verify the hammer CLI tool functions correctly after the change.

Fix this in Satellite Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0241 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0241 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data