Uber

Kraken agents are vulnerable to cache poisoning because they rely on CRC32 checksums instead of SHA-256 digests to verify peer-to-peer blobs, enabling malicious peers to inject unauthorized container images.