cocoon
Affected
- introduced
0.0.0-0, fixed0.4.0(semver)
Fixed versions
0.4.0
Fix
- Fixed version
0.4.0cargo update -p cocoon --precise 0.4.0
Advisory
Also known as: CVE-2024-21530, GHSA-6878-6wc2-pf5h, GHSA-r2jw-c95q-rj29
Sequential calls of encryption API (encrypt, wrap, and dump) result in nonce reuse
Problem: Trying to create a new encrypted message with the same cocoon
object generates the same ciphertext. It mostly affects MiniCocoon andCocoon objects with custom seeds and RNGs (where StdRng is used under
the hood).
Note: The issue does NOT affect objects created with `Cocoon::new`
which utilizes ThreadRng.
Cause: StdRng produces the same nonce because StdRng::clone resets its
state.
Measure: Make encryption API mutable (encrypt, wrap, and dump).
Workaround: Create a new cocoon object with a new seed per each
encryption.
How to Reproduce
let cocoon = MiniCocoon::from_password(b"password", &[1; 32]);
let mut data1 = "my secret data".to_owned().into_bytes();
let _ = cocoon.encrypt(&mut data1)?;
let mut data2 = "my secret data".to_owned().into_bytes();
let _ = cocoon.encrypt(&mut data2)?;
// data1: [23, 217, 251, 151, 179, 62, 85, 15, 253, 92, 192, 112, 200, 52]
// data2: [23, 217, 251, 151, 179, 62, 85, 15, 253, 92, 192, 112, 200, 52]
Workaround
For cocoon <= 0.3.3, create a new cocoon with a different seed
per each encrypt/wrap/dump call.
let cocoon = MiniCocoon::from_password(b"password", &[1; 32]);
let mut data1 = "my secret data".to_owned().into_bytes();
let _ = cocoon.encrypt(&mut data1)?;
// Another seed: &[2; 32].
let cocoon = MiniCocoon::from_password(b"password", &[2; 32]);
let mut data2 = "my secret data".to_owned().into_bytes();
let _ = cocoon.encrypt(&mut data2)?;
// data1: [23, 217, 251, 151, 179, 62, 85, 15, 253, 92, 192, 112, 200, 52]
// data2: [53, 223, 209, 96, 130, 99, 209, 108, 83, 189, 123, 81, 19, 1]Medium Basis: CVSS v3 score 4.5, vector CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
0.0.0-0, fixed 0.4.0 (semver)0.4.0
0.4.0cargo update -p cocoon --precise 0.4.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0