Quick answers
- Is CVE-2020-26245 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-26245 being exploited in the wild.
- How severe is CVE-2020-26245?
- Low severity, with a CVSS score of 3.1, published 27 November 2020.
- Which products and versions are affected?
- systeminformation (npm) SEMVER:introduced=0,fixed=4.30.5.
- Is there a fix for CVE-2020-26245?
- Yes. systeminformation (npm): upgrade to 4.30.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-26245 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-26245?
- Check whether you run systeminformation (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
- systeminformation (npm): upgrade to 4.30.5 or later
npm install systeminformation@4.30.5
Technical details
The vulnerability is a command injection flaw introduced via prototype pollution in the systeminformation library. The root cause is insufficient shell sanitization in the si.inetChecksite() function, which accepts service parameter strings that are not properly validated before being used in shell command execution. An attacker can exploit this by crafting malicious service parameter strings containing shell metacharacters or command injection payloads, bypassing the intended parameter handling through prototype pollution techniques. This allows remote code execution on the affected system. The fix involves a rewrite of shell sanitation logic to prevent prototype pollution. All versions prior to 4.30.5 are affected; users should upgrade immediately or sanitize service parameter inputs as a workaround.
Affected products
- sebhildebrandt systeminformation < 4.30.5
Identifiers
- CVE-2020-26245
- GHSA-4v2w-h9jm-mqjg
Timeline
- 2020-11-27: disclosed: Advisory published
- 2020-11-26: patched: Fix released in version 4.30.5