First published: Mon Sep 25 2017(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Pulp Project | =2.4.0 | |
Pulp Project | =2.4.1 | |
Pulp Project | =2.4.2 | |
Pulp Project | =2.4.3 | |
Pulp Project | =2.4.4 | |
Pulp Project | =2.5.0 | |
Pulp Project | =2.5.1 | |
Pulp Project | =2.5.2 | |
Pulp Project | =2.5.3 | |
Pulp Project | =2.6.0 | |
Pulp Project | =2.6.1 | |
Pulp Project | =2.6.2 | |
Pulp Project | =2.6.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5263 has a medium severity rating due to its potential impact on secure communications.
To fix CVE-2015-5263, upgrade to Pulp versions 2.6.4 or later, which includes a patch for this vulnerability.
CVE-2015-5263 affects Pulp versions 2.4.0 to 2.6.3.
The risk associated with CVE-2015-5263 is that unverified TLS certificates can allow man-in-the-middle attacks.
No, CVE-2015-5263 is not a remote code execution vulnerability; it primarily compromises secure communication.