CVE-2019-1543 ChaCha20-Poly1305 with long nonces

High 7.4 Published Updated

Applications using OpenSSL ChaCha20-Poly1305 with non-default long nonces may reuse nonces, compromising confidentiality and integrity.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2019-1543?

CVE-2019-1543 is a high-severity vulnerability in Openssl Openssl, published on 6 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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).

Weakness: CWE-330, CWE-327

Which versions are affected by CVE-2019-1543?

It affects 1 product.

Linux distribution packages (6)
openssl-1_1 SUSE:Linux Enterprise Desktop 12 SP4All versions1.1.1-2.9.1
openssl-1_1 SUSE:Linux Enterprise Module for Basesystem 15All versions1.1.0i-4.21.1
openssl-1_1 SUSE:Linux Enterprise Server 12 SP4All versions1.1.1-2.9.1
openssl-1_1 SUSE:Linux Enterprise Server for SAP Applications 12 SP4All versions1.1.1-2.9.1
openssl-1_1 SUSE:Linux Enterprise Software Development Kit 12 SP4All versions1.1.1-2.9.1
openssl-1_1 openSUSE:Leap 15.0All versions1.1.0i-lp150.3.22.3

Products include Openssl Openssl.

How do I fix CVE-2019-1543?

Upgrade to a fixed version.

Is CVE-2019-1543 being exploited?

There is no known exploitation of CVE-2019-1543 in the wild and no public exploit code.

All Openssl Openssl vulnerabilities

Sources

Also known as ALPINE-CVE-2019-1543, CLEANSTART-2023-MI80825, CLEANSTART-2026-IH90619, DEBIAN-CVE-2019-1543, DSA-4475-1, GHSA-qpgr-gj53-5m6w and 4 more.

Is CVE-2019-1543 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free