rustsec-2026-0238
Vulnerability from osv_rustsec
Published
2026-08-09 12:00
Modified
2026-08-09 12:34
Summary
Low-level GCM ignores the operation nonce
Details

In all published versions of dcrypt-algorithms before 2.0.0, the low-level Gcm builder required an operation nonce but derived J0 from the nonce captured by the original Gcm constructor. Multiple operations could therefore silently reuse a nonce even when callers supplied distinct values, compromising confidentiality and authenticity under an affected key.

Version 2.0.0 makes Gcm key-only and passes the operation nonce through IV derivation, encryption, and decryption. It also corrects non-96-bit IV processing, rejects tags shorter than 96 bits, and enforces counter limits. Applications must upgrade, identify affected keys, rotate them, and re-encrypt affected data; updating the implementation cannot restore security after nonce reuse.


{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "crypto-failure"
        ],
        "cvss": null,
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "dcrypt-algorithms",
        "purl": "pkg:cargo/dcrypt-algorithms"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            },
            {
              "fixed": "2.0.0"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "GHSA-h9f2-fgp8-vc4h"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "In all published versions of `dcrypt-algorithms` before 2.0.0, the low-level\n`Gcm` builder required an operation nonce but derived `J0` from the nonce\ncaptured by the original `Gcm` constructor. Multiple operations could therefore\nsilently reuse a nonce even when callers supplied distinct values, compromising\nconfidentiality and authenticity under an affected key.\n\nVersion 2.0.0 makes `Gcm` key-only and passes the operation nonce through IV\nderivation, encryption, and decryption. It also corrects non-96-bit IV\nprocessing, rejects tags shorter than 96 bits, and enforces counter limits.\nApplications must upgrade, identify affected keys, rotate them, and re-encrypt\naffected data; updating the implementation cannot restore security after nonce\nreuse.",
  "id": "RUSTSEC-2026-0238",
  "modified": "2026-08-09T12:34:06Z",
  "published": "2026-08-09T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/dcrypt-algorithms"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2026-0238.html"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/ioi-foundation/dcrypt/security/advisories/GHSA-h9f2-fgp8-vc4h"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ioi-foundation/dcrypt/commit/c99cc86f0ee353010cd202cbcd2c310371b0bbb8"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ioi-foundation/dcrypt/releases/tag/v2.0.0"
    }
  ],
  "related": [],
  "severity": [],
  "summary": "Low-level GCM ignores the operation nonce"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…