CVE-2024-20685 json
Azure Private 5G Core Denial of Service Vulnerability
published 2y ago modified 4mo ago also EUVD-2024-18400
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.5%
- EPSS 5.5% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Azure Private 5G Core Denial of Service Vulnerability
Patch / fix
- Microsoft Azure Private 5G Core 2403.0-2
Is CVE-2024-20685 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
5.53% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Microsoft Azure Private 5G Core
Classification
- Weakness
-
- CWE-130 Improper Handling of Length Parameter Inconsistency
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-20685
vendor-advisory
Sources
- CVE List CVE-2024-20685
- NVD CVE-2024-20685
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.