boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Thursday, November 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2019-1543

OpenSSL OpenSSL — ChaCha20-Poly1305 with long nonces
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   N   H   N   N  U  H  H  N    7.4   .0570   93.2     —
AFFECTED
  Product  Versions                                           Fixed
  OpenSSL  Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b) –  —
TIMELINE
  Nov 28  Reserved by openssl
  Mar 6   Published (CNA: openssl)
  Nov 2   ENRICHED — CVE-2019-1543 (OpenSSL). Received CVSS 7.4 and CPE data from NVD.
CWE-327, CWE-330 · CNA: openssl · CVSS v3.0 · 13 references · NVD status: Modified

Description

ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. RFC 7539 specifies that the nonce value (IV) should be 96 bits (12 bytes). OpenSSL allows a variable nonce length and front pads the nonce with 0 bytes if it is less than 12 bytes. However it also incorrectly allows a nonce to be set of up to 16 bytes. In this case only the last 12 bytes are significant and any additional leading bytes are ignored. It is a requirement of using this cipher that nonce values are unique. Messages encrypted using a reused nonce value are susceptible to serious confidentiality and integrity attacks. If an application changes the default nonce length to be longer than 12 bytes and then makes a change to the leading bytes of the nonce expecting the new value to be a new unique nonce then such an application could inadvertently encrypt messages with a reused nonce. Additionally the ignored bytes in a long nonce are not covered by the integrity guarantee of this cipher. Any application that relies on the integrity of these ignored leading bytes of a long nonce may be further affected. Any OpenSSL internal use of this cipher, including in SSL/TLS, is safe because no such use sets such a long nonce value. However user applications that use this cipher directly and set a non-default nonce length to be longer than 12 bytes may be vulnerable. OpenSSL versions 1.1.1 and 1.1.0 are affected by this issue. Due to the limited scope of affected deployments this has been assessed as low severity and therefore we are not creating new releases at this time. Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k (Affected 1.1.0-1.1.0j).

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
November 28, 2018ReservedReserved by openssl
March 6, 2019PublishedPublished (CNA: openssl)
November 2, 2026ENRICHEDENRICHED — CVE-2019-1543 (OpenSSL). Received CVSS 7.4 and CPE data from NVD.

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
OpenSSLOpenSSL—Fixed in OpenSSL 1.1.1c (Affected 1.1.1-1.1.1b)—

Weaknesses

CWE-327 · CWE-330

References (13)

Related

Authoritative record: CVE-2019-1543 at cve.org

Vendors: openssl

Weaknesses: CWE-327 · CWE-330

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2019-1543 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Thursday, November 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.