Bug 1191538 (CVE-2015-1426) - CVE-2015-1426 facter: potential sensitive information leakage in Facter's Amazon EC2 metadata facts handling
Summary: CVE-2015-1426 facter: potential sensitive information leakage in Facter's Ama...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2015-1426
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1191555 1191556
Blocks: 1191546
TreeView+ depends on / blocked
 
Reported: 2015-02-11 13:26 UTC by Vasyl Kaigorodov
Modified: 2021-02-17 05:39 UTC (History)
39 users (show)

Fixed In Version: Facter 2.4.1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-08-06 20:43:11 UTC
Embargoed:

Attachments (Terms of Use)

Description Vasyl Kaigorodov 2015-02-11 13:26:57 UTC 
An issue exists where sensitive Amazon EC2 IAM instance metadata could be added to an Amazon EC2 node's facts, where a non-privileged local user could access the information via Facter.

Although Amazon’s API allows anyone who can access an EC2 instance to view its instance metadata, facts containing sensitive EC2 instance metadata could be unintentionally exposed through off-host applications that display facts.

Upstream commit that fixes this:
https://github.com/puppetlabs/facter/commit/e546bc546e7fb23ad6b68fcf2059452df4d320dd

External References:

http://puppetlabs.com/security/cve/cve-2015-1426
Comment 1 Vasyl Kaigorodov 2015-02-11 13:49:30 UTC 
Created facter tracking bugs for this issue:

Affects: fedora-all [bug 1191555]
Affects: epel-all [bug 1191556]
Comment 2 Kurt Seifried 2015-08-06 20:34:23 UTC 
This only affects products using puppet/facter to directly interact with Amazon EC2 instances.
Comment 3 Kurt Seifried 2015-08-06 20:43:11 UTC 
Statement:

This issue did not affect the versions of facter as shipped with various Red Hat products as they do not use puppet and facter to control Amazon EC2 instances directly.
Note You need to log in before you can comment on or make changes to this bug.