CVE-2021-21315
CVE-2021-21315 is a high-severity vulnerability (CVSS 3.1 base score 7.1). In this vulnerability, an attacker can send a malicious payload that will exploit the name parameter. CISA added it to the Known Exploited Vulnerabilities catalog on 2022-01-18, with a remediation due date of 2022-02-01 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 90.7% probability of exploitation in the next 30 days, in the 99th percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.1 HIGH
- EPSS
- 90.7% (99th pct)
- CISA KEV
- Exploited
- Published
- 2021-02-16
- Weakness
- CWE-78
System Information Library for Node.JS Command Injection is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://nvd.nist.gov/vuln/detail/CVE-2021-21315
Description
The System Information Library for Node.JS (npm package "systeminformation") is an open source collection of functions to retrieve detailed hardware, system and OS information. In systeminformation before version 5.3.1 there is a command injection vulnerability. Problem was fixed in version 5.3.1. As a workaround instead of upgrading, be sure to check or sanitize service parameters that are passed to si.inetLatency(), si.inetChecksite(), si.services(), si.processLoad() ... do only allow strings, reject any arrays. String sanitation works as expected.
Key Findings
as of 2026-11-22- CISA added CVE-2021-21315 to the KEV catalog 336 days after its CVE record was published.
- Its current EPSS score (90.7%) is higher than that of 73% of CISA KEV entries.
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2025-02-06).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| sebhildebrandt | sebhildebrandt systeminformation | < 5.3.1 |
References
5 linksMailing lists
Other references
Record Details
- Published
- 2021-02-16
- Last updated
- 2025-10-21
- Assigner (CNA)
- GitHub_M
- Credited to
- -
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.