Security vulnerabilities and automated fixes for key derivation issues
3 posts found
A critical vulnerability in `scripts/bench-cpu.js` used a hardcoded static salt (`'byok-relay-salt'`) when deriving encryption keys with scrypt, allowing attackers to decrypt all encrypted credentials if the encryption secret was compromised. The fix replaces the hardcoded salt with cryptographically secure random bytes generated per operation, ensuring each user's encrypted credentials require a unique derived key.
The Frida Android server used PBKDF2WithHmacSHA1And8BIT with only 128 iterations to derive secret keys for device attestation. This critically weak configuration made password brute-forcing trivial, allowing attackers who obtained the derived key to recover the original password in seconds. The fix upgraded to PBKDF2WithHmacSHA256 with 600,000 iterations, meeting modern cryptographic standards.
A critical vulnerability (CVE-2025-6545) in pbkdf2 version 3.1.2 caused the library to silently return predictable key material instead of cryptographically secure keys. This Node.js dependency issue was discovered in the website/package-lock.json file and fixed by upgrading to pbkdf2 3.1.3, preventing potential authentication bypass and data exposure in production systems.