Quick answers
- Is CVE-2019-10807 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-10807 being exploited in the wild.
- How severe is CVE-2019-10807?
- Low severity, with a CVSS score of 3.1, published 24 May 2022.
- Which products and versions are affected?
- blamer (npm) SEMVER:introduced=0,fixed=1.0.1.
- Is there a fix for CVE-2019-10807?
- Yes. blamer (npm): upgrade to 1.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-10807 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-10807?
- Check whether you run blamer (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- blamer (npm): upgrade to 1.0.1 or later
npm install blamer@1.0.1
Technical details
The vulnerability is a command injection flaw (CWE-78) in Blamer's argument handling, where special shell metacharacters in user-supplied arguments are not properly sanitized before being passed to OS command execution. An unauthenticated attacker on the network can supply crafted arguments to the blamer command to inject arbitrary shell commands. This requires no user interaction or authentication. The vulnerability was fixed in version 1.0.1, which was released on 2020-03-09 as part of a rewrite that included proper security hardening of script execution.
Affected products
- Blamer blamer 0 to 1.0.0
Identifiers
- CVE-2019-10807
- GHSA-8cxp-cjm8-fj36
Timeline
- 2020-03-11: disclosed
- 2020-03-09: patched: Version 1.0.1 released with security fix
- 2022-05-24: advisory