Skip to content
Fencer Intel
low 2.1

CVE-2015-1426 json

Puppet Labs Facter allows local users to obtain sensitive Amazon EC2 IAM instance metadata

published 11y ago modified 4mo ago also GHSA-j436-h7hm-rx46 , EUVD-2022-4268

cvss
2.1
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 29%
public exploits
0
none known

Summary

Puppet Labs Facter 1.6.0 through 2.4.0 allows local users to obtains sensitive Amazon EC2 IAM instance metadata by reading a fact for an Amazon EC2 node.

Patch / fix

  • rubygems facter 2.4.1
  • facter Debian 13, Debian 12 2.4.4-1

debian advisories DEBIAN-CVE-2015-1426

Is CVE-2015-1426 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-2015-1426 updated cvss 1.7

facter: potential sensitive information leakage in Facter's Amazon EC2 metadata facts handling

  • Red Hat OpenStack Foreman facter Red Hat Enterprise Linux OpenStack Platform 5 (Icehouse) facter Red Hat Enterprise Linux OpenStack Platform 6 (Juno) facter Red Hat Enterprise MRG 1 facter Red Hat OpenShift Enterprise 2 facter Red Hat OpenStack Platform 4 facter
    +2 more products
    Red Hat Satellite 6 facter Red Hat Subscription Asset Manager facter
    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.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
rubygems facter
>=1.6.0, <2.4.1
2.4.1

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

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.