CVE-2024-10604 json
Identifiable Header Values In Fuchsia Leading To Tracking of The User
published 2025-01-30 21 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-32906
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
Vulnerabilities in the algorithms used by Fuchsia to populate network protocol header fields, specifically the TCP ISN, TCP timestamp, TCP and UDP source ports, and IPv4/IPv6 fragment ID allow for these values to be guessed under circumstances
Patch / fix
- google fuchsia f16, f20
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 21 mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- ndss-symposium.org https://www.ndss-symposium.org/wp-content/uploads/2025-122-paper.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- Google Fuchsia
Classification
- Weakness
-
- CWE-330 Use of Insufficiently Random Values
References
-
fuchsia.googlesource.com
/fuchsia/+/a3c17a4d6b3140f9175d6cf6ac4eb4e775f8dea8
patch
-
fuchsia.googlesource.com
/fuchsia/+/40e7fbcdcd013441daf4492f1ead349a9e5b80dc
patch
-
ndss-symposium.org
/wp-content/uploads/2025-122-paper.pdf
exploit, mitigation, third-party-advisory
Sources
- CVE List CVE-2024-10604
- NVD CVE-2024-10604
Fencer Vulns 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.