What is CVE-2019-19010?

CVE-2019-19010 is a critical-severity code injection vulnerability in limnoria (pip), affecting versions < 2019.11.09. It is fixed in 2019.11.09. Untrusted input is evaluated as executable code within the application's runtime environment.

How severe is CVE-2019-19010?

CVE-2019-19010 has a CVSS score of 9.8 (Critical). 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 limnoria are affected by CVE-2019-19010?

limnoria (pip) versions < 2019.11.09 is affected.

Is there a fix for CVE-2019-19010?

Yes. CVE-2019-19010 is fixed in 2019.11.09. Upgrade to this version or later.

Is CVE-2019-19010 exploitable, and should I be worried?

Whether CVE-2019-19010 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-2019-19010 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-2019-19010 in limnoria

Q: How severe is CVE-2019-19010?

CVE-2019-19010 has a CVSS score of 9.8 (Critical). 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 limnoria are affected by CVE-2019-19010?

limnoria (pip) versions < 2019.11.09 is affected.

Q: Is there a fix for CVE-2019-19010?

Yes. CVE-2019-19010 is fixed in 2019.11.09. Upgrade to this version or later.

Q: Is CVE-2019-19010 exploitable, and should I be worried?

Whether CVE-2019-19010 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-2019-19010 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-2019-19010?

Upgrade limnoria to 2019.11.09 or later.

Summary

Eval injection in Supybot/Limnoria

Eval injection in the Math plugin of Limnoria (before 2019.11.09) and Supybot (through 2018-05-09) allows remote unprivileged attackers to disclose information or possibly have unspecified other impact via the calc and icalc IRC commands.

Impact

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2019-19010 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no 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 (2019.11.09); upgrading removes the vulnerable code path.

Affected versions

limnoria (< 2019.11.09)

Security releases

limnoria → 2019.11.09 (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 limnoria to 2019.11.09 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-2019-19010? CVE-2019-19010 is a critical-severity code injection vulnerability in limnoria (pip), affecting versions < 2019.11.09. It is fixed in 2019.11.09. Untrusted input is evaluated as executable code within the application's runtime environment.
How severe is CVE-2019-19010? CVE-2019-19010 has a CVSS score of 9.8 (Critical). 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 limnoria are affected by CVE-2019-19010? limnoria (pip) versions < 2019.11.09 is affected.
Is there a fix for CVE-2019-19010? Yes. CVE-2019-19010 is fixed in 2019.11.09. Upgrade to this version or later.
Is CVE-2019-19010 exploitable, and should I be worried? Whether CVE-2019-19010 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-2019-19010 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-2019-19010? Upgrade limnoria to 2019.11.09 or later.