Remote code execution
Published Mar 20, 2020 · Updated Aug 4, 2024
Code injection in Andrey Kucherenko blamer 1.0.0 and earlier allows remote attackers to execute code via attacker-controlled input. The public HackerOne reference and GitHub advisory do not identify the affected API, code path, or unsafe operation that processes the input. Exploitation requires a consuming application to pass attacker-controlled data into the package, after which injected code runs with the Node.js process's permissions.
Summary
What happened
Code injection in Andrey Kucherenko blamer 1.0.0 and earlier allows remote attackers to execute code via attacker-controlled input. The public HackerOne reference and GitHub advisory do not identify the affected API, code path, or unsafe operation that processes the input. Exploitation requires a consuming application to pass attacker-controlled data into the package, after which injected code runs with the Node.js process's permissions.
The record
- CVE
- CVE-2020-8137
- Published
- Mar 20, 2020
- Updated
- Aug 4, 2024
- Vendor
- Andrey Kucherenko
- Product
- blamer
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Fixed Version: 1.0.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo