Quick answers
- Is CVE-2020-26274 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2020-26274 being exploited in the wild.
- How severe is CVE-2020-26274?
- Low severity, with a CVSS score of 3.1, published 16 December 2020.
- Which products and versions are affected?
- systeminformation (npm) SEMVER:introduced=0,fixed=4.31.1.
- Is there a fix for CVE-2020-26274?
- Yes. systeminformation (npm): upgrade to 4.31.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2020-26274 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2020-26274?
- 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.31.1 or later
npm install systeminformation@4.31.1
Technical details
The vulnerability is a command injection flaw (CWE-78) in the inetLatency() function caused by insufficient sanitization of shell string parameters. An attacker who can pass malicious input to the service parameter can inject arbitrary shell commands for execution. The attack requires an authenticated caller with access to invoke the inetLatency() function. The vulnerability was resolved by implementing proper shell string sanitation in version 4.31.1. All versions prior to 4.31.1 are affected.
Affected products
- systeminformation systeminformation < 4.31.1
Identifiers
- CVE-2020-26274
- GHSA-m57p-p67h-mq74
Timeline
- 2020-12-16: disclosed
- 2020-12-16: patched: Version 4.31.1 released with shell string sanitization fix