CVE-2013-7450
First published: Tue Apr 19 2016(Updated: )
Pulp before 2.3.0 uses the same the same certificate authority key and certificate for all installations.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/pulp | <2.3.0 | 2.3.0 |
| Pulp Project | <=2.2.1-1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://seclists.org/oss-sec/2016/q2/99
- https://github.com/pulp/pulp/pull/627
- https://bugzilla.redhat.com/show_bug.cgi?id=1328345
- http://www.openwall.com/lists/oss-security/2016/04/18/11
- http://www.openwall.com/lists/oss-security/2016/04/18/5
- http://www.openwall.com/lists/oss-security/2016/05/20/1
- https://bugzilla.redhat.com/show_bug.cgi?id=1003326
Frequently Asked Questions
What is the severity of CVE-2013-7450?
CVE-2013-7450 is considered a high-severity vulnerability due to the potential for man-in-the-middle attacks.
How do I fix CVE-2013-7450?
To fix CVE-2013-7450, upgrade to Pulp version 2.3.0 or later.
What type of vulnerabilities does CVE-2013-7450 represent?
CVE-2013-7450 represents an issue related to improper certificate management leading to insecure communications.
Can CVE-2013-7450 be exploited remotely?
Yes, CVE-2013-7450 can be exploited remotely if an attacker can intercept the traffic.
What versions of Pulp are affected by CVE-2013-7450?
Pulp versions prior to 2.3.0 are affected by CVE-2013-7450.
- collector/redhat-bugzilla
- alias/CVE-2013-7450
- agent/references
- agent/weakness
- agent/author
- agent/type
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/remedy
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/severity
- agent/description
- package-manager/redhat
- vendor/pulpproject
- canonical/pulp project
- version/pulp project/2.2.1-1