CVE-2019-10777: OS Command Injection
First published: Wed Jan 08 2020(Updated: )
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".
Credit: report@snyk.io
| Affected Software | Affected Version | How to fix |
|---|---|---|
| AWS Lambda | <1.0.5 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2019-10777?
CVE-2019-10777 has a medium severity rating due to the potential for command injection.
How do I fix CVE-2019-10777?
To fix CVE-2019-10777, upgrade aws-lambda to version 1.0.5 or higher.
What software is affected by CVE-2019-10777?
CVE-2019-10777 affects aws-lambda versions prior to 1.0.5.
What types of vulnerabilities does CVE-2019-10777 involve?
CVE-2019-10777 involves command injection vulnerabilities due to unsanitized input.
Is CVE-2019-10777 exploitable in production systems?
Yes, CVE-2019-10777 is exploitable if the vulnerable version of aws-lambda is used in production.
- agent/softwarecombine
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/last-modified-date
- agent/weakness
- agent/severity
- agent/author
- agent/event
- agent/description
- agent/first-publish-date
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/amazon
- canonical/aws lambda