CVE-2023-38101
Netgear Prosafe Network Management System ≤ 1.7.0.20
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-38101 is a high-severity Exposed Dangerous Method or Function (CWE-749) vulnerability in Netgear Prosafe Network Management System. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-38101 is a remote code execution vulnerability in the NETGEAR ProSAFE Network Management System, specifically within the SettingConfigController class. The flaw stems from an exposed dangerous function that permits arbitrary code execution in the context of the SYSTEM account. Although the vulnerability requires authentication, the existing mechanism can be bypassed, and it carries a CVSS score of 8.8.
Remote attackers with network access can exploit the issue to run arbitrary code on affected installations after bypassing authentication controls. Successful exploitation grants full system-level privileges on the target NETGEAR ProSAFE NMS deployment.
NETGEAR has released a security advisory addressing this and related issues under PSV-2023-0024 and PSV-2023-0025, with corresponding details also published by the Zero Day Initiative as ZDI-23-915; administrators should consult the vendor bulletin for patch availability and recommended remediation steps. The associated EPSS score remains low and unchanged at 0.0570.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-41927
Vulnerability Data
NETGEAR ProSAFE Network Management System SettingConfigController Exposed Dangerous Function Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of NETGEAR ProSAFE Network Management System. Although authentication is required to exploit this vulnerability, the…
more
existing authentication mechanism can be bypassed. The specific flaw exists within the SettingConfigController class. The issue results from an exposed dangerous function. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. . Was ZDI-CAN-19725.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 2 OS baselines
V8.2.1
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized callers from invoking dangerous API methods or functions.
Least privilege restricts which users or processes may reach dangerous methods, limiting exposure.
Least functionality removes or disables non-essential dangerous methods from the exposed interface altogether.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Enforcing least-privilege authorization directly prevents unrestricted dangerous API methods.
Secure SDLC practices stop developers from exposing dangerous functions in the first place.
Vulnerability identification processes will surface exposed dangerous methods during assessment.
Logical access controls at the network/environment layer can limit reachability of exposed functions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect exposed dangerous functions, but does not prevent their initial introduction.
Restricting privileged utility programs reduces exposure of dangerous functions, but does not eliminate the underlying weakness.
Privileged access rights limit who can invoke dangerous methods, but do not address whether the method itself should exist.
Secure development life cycle requires removal or protection of dangerous APIs during design and coding.
Application security requirements can mandate that dangerous methods are not exposed in interfaces.
Secure architecture principles discourage exposing dangerous functions, but do not guarantee their absence.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Ubuntu 22.04 (3 rules)
- V-260559 Ubuntu 22.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749
- V-260529 Ubuntu 22.04 LTS must be configured so that remote X connections are disabled, unless to fulfill documented and validated mission requirements. prevents CWE-749
- V-260557 Ubuntu 22.04 LTS must be configured to use AppArmor. prevents CWE-749
Ubuntu 24.04 (1 rule)
- V-270748 Ubuntu 24.04 LTS must ensure only users who need access to security functions are part of sudo group. prevents CWE-749