“CryptAcquireContext may silently fail in unusual scenarios” is the most troubling of the four bugs, but this is due to the improper use of the so-called CryptAcquireContext function in Windows. The most straightforward way to exploit this would be using native code, potentially delivered through NaCl in Chrome however, the simplest method of exploitation through that attack vector was recently closed off. While CS believes these calls will succeed in all normal scenarios,at least one unusual scenario would cause the calls to fail and rely on poor sources of entropy it is unclear in what additional situations they may fail.Īdditionally, CS identified that volume header decryption relies on improper integrity checks to detect tampering, and that the method of mixing the entropy of keyfiles was not cryptographically sound.įinally, CS identified several included AES implementations that may be vulnerable to cache-timing attacks. The most severe finding relates to the use of the Windows API to generate random numbers for master encryption key material among other things. AES implementation susceptible to cache timing attacks (high). CryptAcquireContext may silently fail in unusual scenarios (high).Unauthenticated ciphertext in volume headers (undetermined).Keyfile mixing is not cryptographically sound (low).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |