What is CVE-2019-10777?

CVE-2019-10777 is a critical-severity OS command injection vulnerability in aws-lambda (npm), affecting versions <= 1.0.4. It is fixed in 1.0.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.

How severe is CVE-2019-10777?

CVE-2019-10777 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 aws-lambda are affected by CVE-2019-10777?

aws-lambda (npm) versions <= 1.0.4 is affected.

Is there a fix for CVE-2019-10777?

Yes. CVE-2019-10777 is fixed in 1.0.5. Upgrade to this version or later.

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

Whether CVE-2019-10777 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-10777 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-10777 in aws-lambda

Q: How severe is CVE-2019-10777?

CVE-2019-10777 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 aws-lambda are affected by CVE-2019-10777?

aws-lambda (npm) versions <= 1.0.4 is affected.

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

Yes. CVE-2019-10777 is fixed in 1.0.5. Upgrade to this version or later.

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

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

Upgrade aws-lambda to 1.0.5 or later.

Summary

OS command injection in aws-lambda

In aws-lambda versions prior to version 1.0.5, the "config.FunctioName" is used to construct the argument used within the "exec" function without any sanitization. It is possible for a user to inject arbitrary commands to the "zipCmd" used within "config.FunctionName".

Impact

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

CVE-2019-10777 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 (1.0.5); upgrading removes the vulnerable code path.

Affected versions

aws-lambda (<= 1.0.4)

Security releases

aws-lambda → 1.0.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

Upgrade aws-lambda to 1.0.5 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-10777? CVE-2019-10777 is a critical-severity OS command injection vulnerability in aws-lambda (npm), affecting versions <= 1.0.4. It is fixed in 1.0.5. Untrusted input reaches a shell command, allowing arbitrary commands to run on the host.
How severe is CVE-2019-10777? CVE-2019-10777 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 aws-lambda are affected by CVE-2019-10777? aws-lambda (npm) versions <= 1.0.4 is affected.
Is there a fix for CVE-2019-10777? Yes. CVE-2019-10777 is fixed in 1.0.5. Upgrade to this version or later.
Is CVE-2019-10777 exploitable, and should I be worried? Whether CVE-2019-10777 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-10777 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-10777? Upgrade aws-lambda to 1.0.5 or later.