Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2012-3867: lib/puppet/ssl/certificate_authority.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not…

MediumCVSS 4.3 · v2.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 18/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.6% of all records.
  • Fixed version: puppet (Debian:11) 2.7.18-1; puppet (Debian:6.0) 2.6.2-5+squeeze6; puppet (RubyGems) 2.7.18, 2.6.17.

Low priority for now. Upgrade to puppet (Debian:11) 2.7.18-1; puppet (Debian:6.0) 2.6.2-5+squeeze6; puppet (RubyGems) 2.7.18, 2.6.17 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

lib/puppet/ssl/certificate_authority.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, does not properly restrict the characters in the Common Name field of a Certificate Signing Request (CSR), which makes it easier for user-assisted remote attackers to trick administrators into signing a crafted agent certificate via ANSI control sequences.

Published
Aug 6, 2012
Updated
Jun 16, 2026
EPSS
2.4% · 84th percentile

Report tools

JSON

Action score

18

Monitor

Low priority for now.

CVSS
17 / 40 · 4.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.4%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2012-3867

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for puppet records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
puppetpuppet
puppetpuppet enterprise
puppetlabspuppet
debiandebian linux
canonicalubuntu linux
opensuseopensuse
suselinux enterprise desktop
suselinux enterprise server

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux10.04
  • canonical ubuntu linux11.04
  • canonical ubuntu linux11.10
  • canonical ubuntu linux12.04
  • debian debian linux6.0
  • opensuse opensuse11.4
  • opensuse opensuse12.1
  • puppet puppet2.6.0
+12 more rows
  • puppet puppet2.6.1
  • puppet puppet2.6.10
  • puppet puppet2.6.11
  • puppet puppet2.6.12
  • puppet puppet2.6.13
  • puppet puppet2.6.14
  • puppet puppet2.6.15
  • puppet puppet2.6.2
  • puppet puppet2.6.3
  • puppet puppet2.6.4
  • puppet puppet2.6.5
  • puppet puppet2.6.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11puppetbefore 2.7.18-12.7.18-1
Debian:6.0puppetbefore 2.6.2-5+squeeze62.6.2-5+squeeze6
RubyGemspuppetfrom 2.7.0 · before 2.7.182.7.18
RubyGemspuppetbefore 2.6.172.6.17

Same product

puppet: all records

Other highest-scoring records for the same primary product.

  • CVE-2016-2785Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might allow remote attackers…
    40Plan
  • CVE-2013-1640The (1) template and (2) inline_template functions in the master server in Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before…
    37Monitor
  • CVE-2021-27021A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to delete tables via an SQL…
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2012-3865Aug 6, 2012 · Directory traversal vulnerability in lib/puppet/reports/store.rb in Puppet before 2.6.17 and 2.7.x before 2.7.18, and Puppet Enterprise…
    15Monitor
  • ← EarlierCVE-2012-3866Aug 6, 2012 · lib/puppet/defaults.rb in Puppet 2.7.x before 2.7.18, and Puppet Enterprise before 2.5.2, uses 0644 permissions for last_run_report.yaml…
    8Monitor
  • Later →CVE-2013-1652Mar 20, 2013 · Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before 3.1.1, and Puppet Enterprise before 1.2.7 and 2.7.x before 2.7.2 allows remote…
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:puppet2.7.18-1 · Debian:11Package registry (OSV)
RubyGems:puppet2.6.17Package registry (OSV)
RubyGems:puppet2.7.18Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

    If successful

    Confidentiality
    none
    Integrity
    P · data or configuration can be modified
    Availability
    none
    Attack complexity
    M
    Confidentiality impact
    None
    Integrity impact
    P
    Availability impact
    None

    Weakness class (CWE)

    CWE-264 · Permissions, Privileges, and Access Controls

    CVSS vector

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

    nvd-primary

    Attack context

    MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

    MITRE has no CAPEC/ATT&CK mapping for this CWE.

    References

    Show all references (6 more)

    Vendor advisories and official records. Exploit/PoC links are deliberately left out.

    All records