All the vulnerabilities related to the version 0.0.0 of the package
Command Injection Vulnerability
command injection vulnerability
Problem was fixed with a parameter check. Please upgrade to version >= 5.3.1
If you cannot upgrade, 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.
Prototype Pollution in systeminformation
command injection vulnerability by prototype pollution
Problem was fixed with a rewrite of shell sanitations to avoid prototyper pollution problems. Please upgrade to version >= 4.30.2
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()
If you have any questions or comments about this advisory:
OS Command Injection in systeminformation
This affects the package systeminformation before 4.30.2. The attacker can overwrite the properties and functions of an object, which can lead to executing OS commands.
systeminformation command injection vulnerability
command injection vulnerability
Problem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.27.11
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetChecksite()
Are there any links users can visit to find out more?
If you have any questions or comments about this advisory:
Systeminformation has command injection vulnerability in getWindowsIEEE8021x (SSID)
The SSID is not sanitized when before it is passed as a parameter to cmd.exe in the getWindowsIEEE8021x function. This means that malicious content in the SSID can be executed as OS commands.
I have exploited this vulnerability in a Windows service using version 5.22.11 of the module, to escalate privileges (in an environment where I am authorized to do so). However, as far as I can see from the code, it is still present in master branch at time of writing, on line 403/404 of network.js.
The SSID is obtained from netsh wlan show interface ... in getWindowsWirelessIfaceSSID, and then passed to cmd.exe /d /s /c "netsh wlan show profiles ... in getWindowsIEEE8021x, without sanitization.
First, the command injection payload should be included in the connected Wi-Fi SSID. For example create hotspot on mobile phone or other laptop, set SSID to payload, connect to it with victim Windows system. Two example SSID's to demonstrate exploitation are below.
Demonstration to run ping command indefinitely:
a" | ping /t 127.0.0.1 &
Run executable with privileges of the user in which vulnerable function is executed. Chosen executable should should be placed in (assuming system drive is C): C:\a\a.exe.
a" | %SystemDrive%\a\a.exe &
Then, the vulnerable function can be executed on the victim system, for example, using:
const si = require('systeminformation');
si.networkInterfaces((net) => { console.log(net) });
Now the chosen command, PING.exe or a.exe will be run through the cmd.exe command line.
This vulnerability may enable an attacker, depending on how the package is used, to perform remote code execution or local privilege escalation.
Command Injection in systeminformation
command injection vulnerability
Problem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.26.2
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to is.services(), is.inetChecksite(), si.inetLatency(), si.networkStats(), is.services() and si.processLoad()
Are there any links users can visit to find out more?
If you have any questions or comments about this advisory:
Command Injection Vulnerability in systeminformation
command injection vulnerability
Problem was fixed with a parameter check. Please upgrade to version >= 5.6.4
If you cannot upgrade, 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.
Command Injection Vulnerability in systeminformation
command injection vulnerability
Problem was fixed with a shell string sanitation fix. Please upgrade to version >= 4.31.1
If you cannot upgrade, be sure to check or sanitize service parameter strings that are passed to si.inetLatency()
If you have any questions or comments about this advisory: