Cross-site device tracking via predictable header values
Published Jan 30, 2025 · Updated Feb 24, 2025
Network-header randomness flaws in Fuchsia before F16 and F17 through F19 allow remote attackers to derive stable device identifiers. The gVisor-based network stack uses a 31-bit Go PRNG, invertible Jenkins hashes, undersized hash keys, and collision-prone IP ID tables to populate TCP and IP fields. The demonstrated tracking path runs site JavaScript and observes generated headers to recover identifiers across sites, networks, and private-browsing sessions.
Summary
What happened
Network-header randomness flaws in Fuchsia before F16 and F17 through F19 allow remote attackers to derive stable device identifiers. The gVisor-based network stack uses a 31-bit Go PRNG, invertible Jenkins hashes, undersized hash keys, and collision-prone IP ID tables to populate TCP and IP fields. The demonstrated tracking path runs site JavaScript and observes generated headers to recover identifiers across sites, networks, and private-browsing sessions.
The record
- CVE
- CVE-2024-10604
- Published
- Jan 30, 2025
- Updated
- Feb 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-330
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2025CVE publishedPublication date reported by the CVE source.
- Feb 24, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- You Can Rand but You Can't Hide proof of conceptfunctional · demonstrated
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