CVE-2024-10026: Improved Seeding and Hashing In gVisor
First published: Thu Jan 30 2025(Updated: )
A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP address and a per-boot identifier that could aid in tracking of a device in certain circumstances.
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google gVisor |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-10026?
CVE-2024-10026 is rated as having a medium severity due to the potential for remote attackers to track devices.
How do I fix CVE-2024-10026?
To mitigate CVE-2024-10026, it is recommended to update to the latest version of Google gVisor where the hashing algorithm and secret sizes have been improved.
What products are affected by CVE-2024-10026?
CVE-2024-10026 specifically affects the Google gVisor software.
What vulnerabilities are linked to weak hashing algorithms in CVE-2024-10026?
CVE-2024-10026 highlights vulnerabilities associated with weak hashing algorithms that could lead to device tracking.
Can CVE-2024-10026 lead to remote exploitation?
Yes, CVE-2024-10026 allows remote attackers to calculate local IP addresses which can aid in tracking devices.
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/references
- agent/weakness
- agent/title
- agent/type
- agent/first-publish-date
- agent/description
- agent/event
- agent/author
- agent/last-modified-date
- agent/severity
- agent/source
- agent/softwarecombine
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/google
- canonical/google gvisor