rustsec-2019-0029
Vulnerability from osv_rustsec
Published
2019-10-22 12:00
Modified
2023-06-13 13:10
Summary
ChaCha20 counter overflow can expose repetitions in the keystream
Details

The ChaCha20 stream cipher can produce a maximum of 2^32 blocks (~256GB) before the 32-bit counter overflows. Releases of the chacha20 crate prior to v0.2.3 allow generating keystreams larger than this, including seeking past the limit. When this occurs, the keystream is duplicated, with failure modes similar to nonce reuse (i.e. exposure of the XOR of two plaintexts).

The v0.2.3 release now panics in this event, rather than exposing the duplicated keystream. Note this is a "hot fix" solution to the problem and future releases will pursue returning an error in this case.

Users of the chacha20poly1305 crate are unaffected by this as this crate properly asserts the length of the plaintext is less than the maximum allowed (P_MAX as described in RFC 8439 Section 2.8).


{
  "affected": [
    {
      "database_specific": {
        "categories": [
          "crypto-failure"
        ],
        "cvss": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
        "informational": null
      },
      "ecosystem_specific": {
        "affected_functions": null,
        "affects": {
          "arch": [],
          "functions": [],
          "os": []
        }
      },
      "package": {
        "ecosystem": "crates.io",
        "name": "chacha20",
        "purl": "pkg:cargo/chacha20"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0.0.0-0"
            },
            {
              "fixed": "0.2.3"
            }
          ],
          "type": "SEMVER"
        }
      ],
      "versions": []
    }
  ],
  "aliases": [
    "CVE-2019-25005",
    "GHSA-j2r6-2m5c-vgh5"
  ],
  "database_specific": {
    "license": "CC0-1.0"
  },
  "details": "The ChaCha20 stream cipher can produce a maximum of 2^32 blocks (~256GB)\nbefore the 32-bit counter overflows. Releases of the `chacha20` crate prior\nto v0.2.3 allow generating keystreams larger than this, including seeking\npast the limit. When this occurs, the keystream is duplicated, with failure\nmodes similar to nonce reuse (i.e. exposure of the XOR of two plaintexts).\n\nThe v0.2.3 release now panics in this event, rather than exposing the\nduplicated keystream. Note this is a \"hot fix\" solution to the problem\nand future releases will pursue returning an error in this case.\n\nUsers of the `chacha20poly1305` crate are unaffected by this as this crate\nproperly asserts the length of the plaintext is less than the maximum allowed\n(`P_MAX` as described in RFC 8439 Section 2.8).",
  "id": "RUSTSEC-2019-0029",
  "modified": "2023-06-13T13:10:24Z",
  "published": "2019-10-22T12:00:00Z",
  "references": [
    {
      "type": "PACKAGE",
      "url": "https://crates.io/crates/chacha20"
    },
    {
      "type": "ADVISORY",
      "url": "https://rustsec.org/advisories/RUSTSEC-2019-0029.html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/RustCrypto/stream-ciphers/pull/64"
    }
  ],
  "related": [],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "ChaCha20 counter overflow can expose repetitions in the keystream"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

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…