CyberRota Analysis
AI-GeneratedVeraCrypt versions prior to 1.26.29 are vulnerable in non-default builds configured with WOLFCRYPT=1, where the key derivation process for SHA-256 and SHA-512 disregards the configured iteration count, allowing attackers to perform more efficient offline password guessing attacks. Users of affected builds should prioritize upgrading to version 1.26.29 or later, as volumes created with the vulnerable configuration require backup and recreation to ensure security. This vulnerability primarily impacts organizations relying on custom VeraCrypt builds for disk encryption.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
VeraCrypt provides disk encryption with strong security based on TrueCrypt. Prior to 1.26.29, non-default builds created with WOLFCRYPT=1 and WOLFCRYPT_BACKEND route SHA-256 and SHA-512 volume-header key derivation through derive_key_sha256 and derive_key_sha512 in src/Crypto/wolfCrypt.c, where the configured iterations value is discarded and wc_HKDF is used instead of PBKDF2-HMAC. Changing the PIM or iteration count therefore does not increase derivation cost, allowing an attacker with an affected container, disk image, or volume header to perform substantially cheaper offline password guesses. Official precompiled VeraCrypt binaries and normal distribution packages use the standard PBKDF2 backend and are not affected. Volumes created by an affected WOLFCRYPT=1 build require backup and recreation because corrected builds derive different keys. This issue is fixed in version 1.26.29.