High severity · published Jun 8, 2017
CVE-2016-3112
client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to…
7.5
CVSS
2.2%
EPSS
No
On KEV
Description
client/consumer/cli.py in Pulp before 2.8.3 writes consumer private keys to etc/pki/pulp/consumer/consumer-cert.pem as world-readable, which allows remote authenticated users to obtain the consumer private keys and escalate privileges by reading /etc/pki/pulp/consumer/consumer-cert, and authenticating as a consumer user.
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)2.2% · higher than 82% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PU
Pulp · Pulpproject
through 2.8.2-1 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2016-3112
CVE.org
https://www.cve.org/CVERecord?id=CVE-2016-3112
Mailing List
http://www.openwall.com/lists/oss-security/2016/05/20/1
access.redhat.com
https://access.redhat.com/errata/RHBA-2016:1501
Issue Tracking
https://bugzilla.redhat.com/attachment.cgi?id=1146538
Issue Tracking
https://bugzilla.redhat.com/show_bug.cgi?id=1326242
Patch
https://pulp.plan.io/issues/1834
More from Pulp
8.3
CVE-2024-7143
A flaw was found in the Pulp package
8.1
CVE-2015-5263
pulp-consumer-client 2.4.0 through 2.6.3 does not check the server's TLS certificate signatures when retrieving the server's public key upon registration
7.5
CVE-2018-1090
In Pulp before version 2.16.2, secrets are passed into override_config when triggering a task and then become readable to all users with read access on the distributor/importer
7.5
CVE-2016-3704
Pulp before 2.8.5 uses bash's $RANDOM in an unsafe way to generate passwords
7.5
CVE-2013-7450
Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations