Which versions of portage are affected by CVE-2013-2100?

portage (pip) versions < 2.1.12.2 is affected.

Is there a fix for CVE-2013-2100?

Yes. CVE-2013-2100 is fixed in 2.1.12.2. Upgrade to this version or later.

Is CVE-2013-2100 exploitable, and should I be worried?

Whether CVE-2013-2100 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2013-2100 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2013-2100 in portage

Q: What is CVE-2013-2100?

CVE-2013-2100 is a high-severity security vulnerability in portage (pip), affecting versions < 2.1.12.2. It is fixed in 2.1.12.2.

Q: Is there a fix for CVE-2013-2100?

Yes. CVE-2013-2100 is fixed in 2.1.12.2. Upgrade to this version or later.

Q: Is CVE-2013-2100 exploitable, and should I be worried?

Whether CVE-2013-2100 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2013-2100 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2013-2100?

Upgrade portage to 2.1.12.2 or later.

CVE-2013-2100

CVE-2013-2100 is a high-severity security vulnerability in portage (pip), affecting versions < 2.1.12.2. It is fixed in 2.1.12.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Gentoo Portage does not verify X.509 certificates from SSL servers

The urlopen function in pym/portage/util/_urlopen.py in Gentoo Portage 2.1.12, when using HTTPS, does not verify X.509 certificates from SSL servers, which allows man-in-the-middle attackers to spoof servers and modify binary package lists via a crafted certificate.

Impact

Affected versions

portage (< 2.1.12.2)

Security releases

portage → 2.1.12.2 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade portage to 2.1.12.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2013-2100? CVE-2013-2100 is a high-severity security vulnerability in portage (pip), affecting versions < 2.1.12.2. It is fixed in 2.1.12.2.
Which versions of portage are affected by CVE-2013-2100? portage (pip) versions < 2.1.12.2 is affected.
Is there a fix for CVE-2013-2100? Yes. CVE-2013-2100 is fixed in 2.1.12.2. Upgrade to this version or later.
Is CVE-2013-2100 exploitable, and should I be worried? Whether CVE-2013-2100 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2013-2100 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2013-2100? Upgrade portage to 2.1.12.2 or later.

Other vulnerabilities in portage

CVE-IDSeverityPackage summary

CVE-2016-20021Highportage: Gentoo Portage missing PGP validation of executed code