CVE-2023-4012
Ntpsec 1.2.2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-4012 is a high-severity Incomplete Internal State Distinction (CWE-372) vulnerability in Ntpsec Ntpsec. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-53905
Vulnerability Data
ntpd will crash if the server is not NTS-enabled (no certificate) and it receives an NTS-enabled client request (mode 3).
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
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.
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.
Secure development lifecycle practices can include state-machine validation and invariant checks that reduce incomplete internal state errors.
A.8.26 only requires that security requirements (including resilience against attacks such as SQL injection) be identified and specified during development or acquisition; it does not itself enforce, implement, or prevent the incomplete state distinction from arising or being exploitable.
A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, fail securely, distrust external input, assume-breach, zero-trust verification) plus design reviews that can catch and block many incomplete-state assumptions before they reach code, but leaves a bounded remainder: state-machine logic errors that are not visible in architecture, do not violate any listed principle, and are introduced in detailed implementation rather than high-level design.
Secure coding standards can require defensive checks against invalid or ambiguous internal states.
Security testing can detect state-machine flaws that manifest as incomplete internal state distinction.