CVE-2023-38317: OpenNDS · OS Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 10.1.3 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 65% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 10.1.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Jan 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade opennds/openNDS to 10.1.3.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubopennds/openNDSpkg:github/opennds/openNDSOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
To mitigate CVE-2023-38317, European organizations should immediately upgrade OpenNDS to version 10.1.3 or later, where the vulnerability is patched. If upgrading is not immediately feasible, organizations should restrict access to the OpenNDS configuration files using strict file system permissions and monitor for unauthorized access attempts. Implementing file integrity monitoring can help detect unauthorized changes to configuration files. Network segmentation should be employed to limit access to systems running OpenNDS, reducing exposure to potential attackers. Additionally, organizations should audit and harden related systems to prevent indirect access to configuration files, including reviewing privilege assignments and securing administrative interfaces. Employing application-level whitelisting or command execution restrictions can further reduce risk. Regular vulnerability scanning and penetration testing focused on configuration file access and command injection vectors are recommended to identify and remediate weaknesses proactively.
Description
An issue was discovered in OpenNDS before 10.1.3. It fails to sanitize the network interface name entry in the configuration file, allowing attackers that have direct or indirect access to this file to execute arbitrary OS commands.