What is CVE-2020-4066?

CVE-2020-4066 is a low-severity OS command injection vulnerability in limdu (npm), affecting versions <= 0.9.4. It is fixed in 0.9.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2020-4066?

CVE-2020-4066 has a CVSS score of 3.8 (Low). 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 limdu are affected by CVE-2020-4066?

limdu (npm) versions <= 0.9.4 is affected.

Is there a fix for CVE-2020-4066?

Yes. CVE-2020-4066 is fixed in 0.9.5. Upgrade to this version or later.

Is CVE-2020-4066 exploitable, and should I be worried?

Whether CVE-2020-4066 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-2020-4066 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-2020-4066?

Upgrade limdu to 0.9.5 or later.

CVE-2020-4066 in limdu

Q: How severe is CVE-2020-4066?

CVE-2020-4066 has a CVSS score of 3.8 (Low). 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 limdu are affected by CVE-2020-4066?

limdu (npm) versions <= 0.9.4 is affected.

Q: Is there a fix for CVE-2020-4066?

Yes. CVE-2020-4066 is fixed in 0.9.5. Upgrade to this version or later.

Q: Is CVE-2020-4066 exploitable, and should I be worried?

Whether CVE-2020-4066 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-2020-4066 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-2020-4066?

Upgrade limdu to 0.9.5 or later.

Summary

Command Injection in Limdu

Workarounds

Do not use trainBatch with classifiers that rely on shell execution, such as SVM Perf, SVM Linear or Adaboost

References

Impact

The trainBatch function has a command injection vulnerability. Clients of the Limdu library are unlikely to be aware of this, so they might unwittingly write code that contains a vulnerability.

Untrusted input reaches a shell command, allowing arbitrary commands to run on the host. Typical impact: code execution in the application's environment.

CVE-2020-4066 has a CVSS score of 3.8 (Low). The vector is network-reachable, high 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 (0.9.5); upgrading removes the vulnerable code path.

Affected versions

limdu (<= 0.9.4)

Security releases

limdu → 0.9.5 (npm)

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

Patched in version 0.9.5.

Frequently Asked Questions

What is CVE-2020-4066? CVE-2020-4066 is a low-severity OS command injection vulnerability in limdu (npm), affecting versions <= 0.9.4. It is fixed in 0.9.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2020-4066? CVE-2020-4066 has a CVSS score of 3.8 (Low). 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 limdu are affected by CVE-2020-4066? limdu (npm) versions <= 0.9.4 is affected.
Is there a fix for CVE-2020-4066? Yes. CVE-2020-4066 is fixed in 0.9.5. Upgrade to this version or later.
Is CVE-2020-4066 exploitable, and should I be worried? Whether CVE-2020-4066 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-2020-4066 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-2020-4066? Upgrade limdu to 0.9.5 or later.