Crypto vulns in DuckDB. I don't have a deep understanding of cryptography but these ones are pretty simple to grasp.
https://github.com/duckdb/duckdb/security/advisories/GHSA-vmp8-hg63-v2hp
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()