What is CVE-2015-5301?

CVE-2015-5301 is a medium-severity security vulnerability in ipsilon (pip), affecting versions >= 0.1.0, < 1.0.2. It is fixed in 1.0.2, 1.2.0.

Which versions of ipsilon are affected by CVE-2015-5301?

ipsilon (pip) versions >= 0.1.0, < 1.0.2 is affected.

Is there a fix for CVE-2015-5301?

Yes. CVE-2015-5301 is fixed in 1.0.2, 1.2.0. Upgrade to this version or later.

Is CVE-2015-5301 exploitable, and should I be worried?

Whether CVE-2015-5301 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-2015-5301 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-2015-5301?

Upgrade: ipsilon to 1.0.2 or later, ipsilon to 1.2.0 or later.

CVE-2015-5301 in ipsilon

Q: Which versions of ipsilon are affected by CVE-2015-5301?

ipsilon (pip) versions >= 0.1.0, < 1.0.2 is affected.

Q: Is there a fix for CVE-2015-5301?

Yes. CVE-2015-5301 is fixed in 1.0.2, 1.2.0. Upgrade to this version or later.

Q: Is CVE-2015-5301 exploitable, and should I be worried?

Whether CVE-2015-5301 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-2015-5301 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-2015-5301?

Upgrade: ipsilon to 1.0.2 or later, ipsilon to 1.2.0 or later.

Summary

Ipsilon denial of service by deleting a SAML2 Service Provider (SP)

providers/saml2/admin.py in the Identity Provider (IdP) server in Ipsilon 0.1.0 before 1.0.2 and 1.1.x before 1.1.1 does not properly check permissions, which allows remote authenticated users to cause a denial of service by deleting a SAML2 Service Provider (SP).

Impact

Affected versions

ipsilon (>= 0.1.0, < 1.0.2) ipsilon (>= 1.1.0, < 1.1.1)

Security releases

ipsilon → 1.0.2 (pip) ipsilon → 1.2.0 (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 the following packages to resolve this vulnerability:

ipsilon to 1.0.2 or later; ipsilon to 1.2.0 or later

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

Frequently Asked Questions

What is CVE-2015-5301? CVE-2015-5301 is a medium-severity security vulnerability in ipsilon (pip), affecting versions >= 0.1.0, < 1.0.2. It is fixed in 1.0.2, 1.2.0.
Which versions of ipsilon are affected by CVE-2015-5301? ipsilon (pip) versions >= 0.1.0, < 1.0.2 is affected.
Is there a fix for CVE-2015-5301? Yes. CVE-2015-5301 is fixed in 1.0.2, 1.2.0. Upgrade to this version or later.
Is CVE-2015-5301 exploitable, and should I be worried? Whether CVE-2015-5301 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-2015-5301 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-2015-5301?
- Upgrade ipsilon to 1.0.2 or later
- Upgrade ipsilon to 1.2.0 or later

Other vulnerabilities in ipsilon

CVE-IDSeverityPackage summary

CVE-2015-5217Mediumipsilon: Ipsilon denial of service via a duplicate SP name CVE-2016-8638Criticalipsilon: Session Fixation in ipsilon