What is CVE-2017-11610?

CVE-2017-11610 is a high-severity security vulnerability in supervisor (pip), affecting versions < 3.0.1. It is fixed in 3.0.1, 3.1.4, 3.2.4, 3.3.3.

How severe is CVE-2017-11610?

CVE-2017-11610 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of supervisor are affected by CVE-2017-11610?

supervisor (pip) versions < 3.0.1 is affected.

Is there a fix for CVE-2017-11610?

Yes. CVE-2017-11610 is fixed in 3.0.1, 3.1.4, 3.2.4, 3.3.3. Upgrade to this version or later.

Is CVE-2017-11610 exploitable, and should I be worried?

Whether CVE-2017-11610 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-2017-11610 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-2017-11610 in supervisor

Q: How severe is CVE-2017-11610?

CVE-2017-11610 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of supervisor are affected by CVE-2017-11610?

supervisor (pip) versions < 3.0.1 is affected.

Q: Is there a fix for CVE-2017-11610?

Yes. CVE-2017-11610 is fixed in 3.0.1, 3.1.4, 3.2.4, 3.3.3. Upgrade to this version or later.

Q: Is CVE-2017-11610 exploitable, and should I be worried?

Whether CVE-2017-11610 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-2017-11610 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-2017-11610?

Upgrade: supervisor to 3.0.1 or later, supervisor to 3.1.4 or later, supervisor to 3.2.4 or later, supervisor to 3.3.3 or later.

Summary

Incorrect Default Permissions in Supervisor

The XML-RPC server in supervisor before 3.0.1, 3.1.x before 3.1.4, 3.2.x before 3.2.4, and 3.3.x before 3.3.3 allows remote authenticated users to execute arbitrary commands via a crafted XML-RPC request, related to nested supervisord namespace lookups.

Impact

CVE-2017-11610 has a CVSS score of 8.8 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.1, 3.1.4, 3.2.4, 3.3.3); upgrading removes the vulnerable code path.

Affected versions

supervisor (< 3.0.1) supervisor (>= 3.1.0, < 3.1.4) supervisor (>= 3.2.0, < 3.2.4) supervisor (>= 3.3.0, < 3.3.3)

Security releases

supervisor → 3.0.1 (pip) supervisor → 3.1.4 (pip) supervisor → 3.2.4 (pip) supervisor → 3.3.3 (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:

supervisor to 3.0.1 or later; supervisor to 3.1.4 or later; supervisor to 3.2.4 or later; supervisor to 3.3.3 or later

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

Frequently Asked Questions

What is CVE-2017-11610? CVE-2017-11610 is a high-severity security vulnerability in supervisor (pip), affecting versions < 3.0.1. It is fixed in 3.0.1, 3.1.4, 3.2.4, 3.3.3.
How severe is CVE-2017-11610? CVE-2017-11610 has a CVSS score of 8.8 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of supervisor are affected by CVE-2017-11610? supervisor (pip) versions < 3.0.1 is affected.
Is there a fix for CVE-2017-11610? Yes. CVE-2017-11610 is fixed in 3.0.1, 3.1.4, 3.2.4, 3.3.3. Upgrade to this version or later.
Is CVE-2017-11610 exploitable, and should I be worried? Whether CVE-2017-11610 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-2017-11610 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-2017-11610?
- Upgrade supervisor to 3.0.1 or later
- Upgrade supervisor to 3.1.4 or later
- Upgrade supervisor to 3.2.4 or later
- Upgrade supervisor to 3.3.3 or later