CVE-2023-38323: 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-38323, European organizations should take the following specific actions: 1) Immediately upgrade OpenNDS to version 10.1.3 or later, where the vulnerability has been addressed. 2) Restrict access to the OpenNDS configuration files to only trusted administrators using strict file permissions and access controls to prevent unauthorized modification of the 'status path script' entry. 3) Implement monitoring and alerting for any changes to configuration files or unusual command execution patterns on systems running OpenNDS. 4) Conduct thorough audits of systems running OpenNDS to identify any unauthorized changes or signs of compromise. 5) Employ network segmentation to isolate directory services from less trusted network segments, reducing the risk of indirect access to configuration files. 6) Where possible, apply application-level input validation or sandboxing to limit the impact of command injection. 7) Educate system administrators about the risks of improper configuration file access and the importance of patch management. These steps go beyond generic advice by focusing on access control to configuration files, proactive monitoring, and network architecture considerations specific to directory services.
Description
An issue was discovered in OpenNDS before 10.1.3. It fails to sanitize the status path script entry in the configuration file, allowing attackers that have direct or indirect access to this file to execute arbitrary OS commands.