High severity · published Sep 25, 2017
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
8.1
CVSS
0.9%
EPSS
No
On KEV
Description
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.
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 58% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PU
Pulp · Pulpproject
2.4.0; 2.4.1; 2.4.2; 2.4.3; 2.4.4; 2.5.0; +7 more · source: NVD
Affected product
PU
Pulp
Pulpproject
More from Pulp
8.3
CVE-2024-7143
A flaw was found in the Pulp package
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-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
CVE-2013-7450
Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations