Unauthenticated service interruption via InitialUEMessage length validation
Published Apr 9, 2024 · Updated May 3, 2025
Improper input validation in Microsoft Azure Private 5G Core before 2403.0-2 allows remote attackers to interrupt 5G service. The InitialUEMessage handler fails to validate a length parameter before processing untrusted signaling data, producing a denial-of-service condition. No authentication or user interaction is required, but exploitation has high complexity and interrupts availability across the 5G network.
Summary
What happened
Improper input validation in Microsoft Azure Private 5G Core before 2403.0-2 allows remote attackers to interrupt 5G service. The InitialUEMessage handler fails to validate a length parameter before processing untrusted signaling data, producing a denial-of-service condition. No authentication or user interaction is required, but exploitation has high complexity and interrupts availability across the 5G network.
The record
- CVE
- CVE-2024-20685
- Published
- Apr 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Azure Private 5G Core
- Classifications
- CWE-130, T1498
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <2403.0-2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo