Crypto vulns in DuckDB. I don't have a deep understanding of cryptography but these ones are pretty simple to grasp.

github.com/duckdb/duckdb/secur

  • The DuckDB can fall back to an insecure random number generator (pcg32) to generate cryptographic keys or IVs.

  • When clearing keys from memory, the compiler may remove the memset() and leave sensitive data on the heap

  • By modifying the database header, an attacker could downgrade the encryption mode from GCM to CTR to bypass integrity checks.

  • Failure to check return value on call to OpenSSL rand_bytes()

0

If you have a fediverse account, you can quote this note from your own instance. Search https://infosec.exchange/users/cR0w/statuses/115538907813665068 on your instance and quote it. (Note that quoting is not supported in Mastodon.)