CVE-2024-20685
Microsoft Azure Private 5G Core ≤ 2403.0-2
Raw vector
CVSS:3.1/AV:N/AC:H/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-2024-20685 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Microsoft Azure Private 5G Core. Its CVSS base score is 5.9 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked in the top 7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-18400
Vulnerability Data
Azure Private 5G Core Denial of Service Vulnerability
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.5.5V4.2.1V4.2.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.
Input validation enforces correct length-to-data consistency checks on parsed messages before processing.
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.
Secure SDLC practices directly enforce length validation and input sanitization during coding and review.
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 mandates input validation and length checks that directly address inconsistent length fields.
Application security requirements include explicit rules for handling message lengths and data structures.
A.8.27 mandates security-by-design, defence-in-depth, distrust-external-input, secure session control, data validation/sanitisation and design reviews against known attack patterns; these reach a minority slice of length-parameter inconsistencies (especially where they surface as input-handling or parsing flaws) but leave the bulk of protocol/message-parsing bugs untouched.
Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.
Security testing in development can detect length-inconsistency vulnerabilities before deployment.