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.
The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
| Link | Tags |
|---|---|
| https://github.com/google/gvisor/commit/f956b5ac17ae1f60a4d21999b59ba18c55f86d56 | patch |
| https://github.com/google/gvisor/commit/e54bfde79278cafadedbf73c68ee10cb5982f2af | patch |
| https://github.com/google/gvisor/commit/83f75082e5b03fafca9201d9d9939028f712b0b2 | patch |
| https://www.ndss-symposium.org/wp-content/uploads/2025-122-paper.pdf | third party advisory technical description exploit |