Skip to content
Fencer Intel
low 3.3

CVE-2012-1906 json

Puppet uses predictable filenames, allowing arbitrary file overwrite

published 2012-05-29 14 y ago modified 2026-06-16 4 mo ago also GHSA-c4mc-49hq-q275 , EUVD-2022-3504

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 28%
public exploits
0
none known

Summary

Puppet 2.6.x before 2.6.15 and 2.7.x before 2.7.13, and Puppet Enterprise (PE) Users 1.0, 1.1, 1.2.x, 2.0.x, and 2.5.x before 2.5.1 uses predictable file names when installing Mac OS X packages from a remote source, which allows local users to overwrite arbitrary files or install arbitrary packages via a symlink attack on a temporary file in /tmp.

Patch / fix

  • rubygems puppet 2.6.15, 2.7.13
  • puppet Debian 11 2.7.13-1

debian advisories DEBIAN-CVE-2012-1906

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2012-1906 updated cvss 5.5

puppet: Puppet uses predictable filenames, allowing arbitrary file overwrite

  • Red Hat OpenStack Platform 16.1 puppet, puppet-server, puppet-headless Red Hat OpenStack Platform 16.2 puppet, puppet-server, puppet-headless Red Hat OpenStack Platform 17.0 puppet, puppet-headless Red Hat OpenStack Platform 17.1 puppet, puppet-headless
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 3.3 AV:L/AC:M/Au:N/C:N/I:P/A:P

Affected packages

ecosystem package affected fixed in
rubygems puppet
>=2.6, <2.6.15
>=2.7, <2.7.13
2.6.15
2.7.13

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
  • CWE-377 DEPRECATED: Insecure Temporary File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.