Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

crates.io package

dcrypt-symmetric

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. Unratedcrates.ioPublished

    Streaming AEAD does not authenticate stream structure

    GHSA-8cwp-4826-jg9f

    Affected
    • crates.io dcrypt-symmetric >= 0.0.0-0, < 2.0.0
    Fixed in
    2.0.0· Vendor fix available
    Issue
    In all published versions of `dcrypt-symmetric` before 2.0.0, version-1 GCM and ChaCha20-Poly1305 streams used unauthenticated terminator, counter, and length fields. Decryptors trusted transmitted counters, allocated from unbounded lengths, and discarded plaintext that did not fit a caller's single read buffer. An attacker could obtain successful truncated EOF, omit, replay, or reorder frames within a stream, or request an allocation approaching 4 GiB. Version 2.0.0 introduces the `DCRSTRM2` format, which authenticates its version, algorithm, random stream identifier, base nonce, strict sequence, bounded lengths, final flag, and caller AAD. It enforces authenticated finality and physical EOF, bounds frames to 16 KiB before allocation, retains partial-read plaintext, and rejects legacy version-1 input. Existing version-1 ciphertext cannot retrospectively prove completeness or ordering and must be migrated only through an application-specific, explicitly trusted process.

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

    Sources:osv.devSource checked Evidence →