RUSTSEC-2026-0239
Streaming AEAD does not authenticate stream structure
Details
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.
Are you affected?
Enter the version of the package you're using.
Affected packages
0.0.0-0 Fixed in: 2.0.0 Upgrade dcrypt-symmetric to 2.0.0 or newer (ecosystem crates.io).
References
- https://crates.io/crates/dcrypt-symmetric [PACKAGE]
- https://rustsec.org/advisories/RUSTSEC-2026-0239.html [ADVISORY]
- https://github.com/ioi-foundation/dcrypt/security/advisories/GHSA-8cwp-4826-jg9f [ADVISORY]
- https://github.com/ioi-foundation/dcrypt/commit/c99cc86f0ee353010cd202cbcd2c310371b0bbb8 [WEB]
- https://github.com/ioi-foundation/dcrypt/releases/tag/v2.0.0 [WEB]