Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

cocoon

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 4.5crates.ioPublished

    Sequential calls of encryption API (encrypt, wrap, and dump) result in nonce reuse

    CVE-2024-21530 · GHSA-6878-6wc2-pf5h

    Affected
    • crates.io cocoon < 0.4.0
    Fixed in
    0.4.0· Vendor fix available
    Issue
    Problem: Trying to create a new encrypted message with the same cocoon object generates the same ciphertext. It mostly affects MiniCocoon and Cocoon 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 Workaround For cocoon <= 0.3.3, create a new cocoon with a different seed per each encrypt/wrap/dump call.

    Recommended action: Upgrade to 0.4.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →