dbcve.org
ForemanApplication · Theforeman

CVE-2013-0210

HIGH · 7.5 CVSS v2.0 Published 2014-05-08
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The smart proxy Puppet run API in Foreman before 1.2.0 allows remote attackers to execute arbitrary commands via vectors related to escaping and Puppet commands.

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 · moderate confidence

Command injection vulnerability in Foreman's smart proxy Puppet run API that allows remote attackers to execute arbitrary OS commands through improper escaping of parameters passed to Puppet commands. The vulnerability exists in versions prior to 1.2.0.

MitigationUpgrade Foreman to version 1.2.0 or later. If immediate patching is not feasible, restrict network access to the smart proxy API to trusted sources only.

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
ForemanApplication
Affected:<= 1.0= 0.1= 0.2= 0.3= 0.4= 0.4.1

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
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Identify Foreman version
    Run 'rpm -q foreman' or check /usr/share/foreman/README or the web UI footer version display
    Affected if Installed version is 1.0.x or earlier, or any of these specific versions: 0.1, 0.2, 0.3, 0.4, or 0.4.1
  2. Verify smart proxy feature is enabled
    Check /etc/foreman-proxy/settings.yml or similar configuration file for the 'puppet' proxy module entry
    Affected if Smart proxy is enabled with the Puppet run API module loaded and accessible
  3. Confirm Puppet run API is exposed
    Inspect the smart proxy configuration under /etc/foreman-proxy/settings.d/ for the puppet.yml file and verify the :enabled: setting
    Affected if The Puppet proxy is configured with :enabled: true and is listening on a network-accessible interface
  4. Check API access controls
    Review /etc/foreman-proxy/settings.yml for :trusted_hosts: or :ssl: settings that control API access
    Affected if The API is accessible without authentication or from untrusted hosts, allowing external access to the Puppet run endpoint

You are affected if Foreman version is 1.0 or earlier (including 0.1-0.4.1) AND the smart proxy Puppet run API is enabled and network-accessible.

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
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Upgrade Foreman to version 1.2.0 or later. If immediate patching is not feasible, restrict network access to the smart proxy API to trusted sources only.

Fix this in Foreman Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0210 — 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-2013-0210 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