CVE-2019-1543
published 2019-03-06CVE-2019-1543: 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…
PriorityP348high7.4CVSS 3.0
AVNACHPRNUINSUCHIHAN
EPSS
5.70%
92.1th percentile
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).
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | openssl | < openssl 1.1.1c-1 (bookworm) | openssl 1.1.1c-1 (bookworm) |
| openssl | openssl | — | — |
| openssl | openssl | — | — |
| openssl | openssl | >= 0 < 1.1.1c-1 | 1.1.1c-1 |
| openssl | openssl | >= 0 < 1.1.1c-1 | 1.1.1c-1 |
| openssl | openssl | >= 0 < 1.1.1c-1 | 1.1.1c-1 |
| openssl | openssl | >= 0 < 1.1.1c-1 | 1.1.1c-1 |
| openssl | openssl | 1.1.0 – 1.1.0j | — |
| openssl | openssl | 1.1.1 – 1.1.1b | — |
CVSS provenance
nvdv3.07.4HIGHCVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:N
osv7.4HIGH
vendor_debian7.4LOW
vendor_oracle7.4HIGH
vendor_redhat7.4HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Oracle
Oracle Oracle Enterprise Manager Risk Matrix: Discovery Framework (OpenSSL) — CVE-2019-1543
vendor_oracle·2020-04-15·CVSS 7.4
CVE-2019-1543 [HIGH] Oracle Oracle Enterprise Manager Risk Matrix: Discovery Framework (OpenSSL) — CVE-2019-1543
Oracle Oracle Enterprise Manager Risk Matrix: Discovery Framework (OpenSSL) vulnerability
CVE: CVE-2019-1543
CVSS: 7.4
Protocol: HTTPS
Remote exploit: Yes
Affected versions: Network
Advisory: cpuapr2020 (APR 2020)
Red Hat
openssl: ChaCha20-Poly1305 with long nonces
vendor_redhat·2019-03-06·CVSS 7.4
CVE-2019-1543 [HIGH] CWE-323 openssl: ChaCha20-Poly1305 with long nonces
openssl: ChaCha20-Poly1305 with long nonces
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 b
Debian
CVE-2019-1543: openssl - ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every...
vendor_debian·2019·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543: openssl - ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every...
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
GHSA
GHSA-qpgr-gj53-5m6w: ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation
ghsa_unreviewed·2022-05-13
CVE-2019-1543 [HIGH] CWE-327 GHSA-qpgr-gj53-5m6w: ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation
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
OSV
CVE-2019-1543: ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation
osv·2019-03-06·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543: ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation
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
No detection rules found.
No public exploits indexed.
HackerOne
ChaCha20-Poly1305 with long nonces
hackerone·2019-09-30·CVSS 7.4
CVE-2019-1543 [HIGH] ChaCha20-Poly1305 with long nonces
ChaCha20-Poly1305 with long nonces
This report relates to CVE-2019-1543, https://www.openssl.org/news/secadv/20190306.txt, which I reported to the OpenSSL maintainers a few days ago.
OpenSSL accepts nonces for the AEAD cipher ChaCha20-Poly1305 of up to 16-bytes. This support is advertised in the OpenSSL documentation and via the CHACHA_CTR_SIZE (16) constant.
However, the specification for ChaCha20-Poly1305 supports only up to 12-bytes.
If a user passes a 16-byte nonce to OpenSSL, OpenSSL will discard the first 4-bytes of the nonce.
## Impact
The maintainers classified the severity of this as LOW since it only affects user applications of OpenSSL, while at the same time recognizing the severity of this for these user applications as MEDIUM (or "serious" and "catastrophic" in the word
Bugzilla
CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [epel-7]
bugzilla·2019-04-03·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [epel-7]
CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
Use the following template to for the '
Bugzilla
CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
bugzilla·2019-04-03·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported versions of Fed
Bugzilla
CVE-2019-1543 compat-openssl10: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
bugzilla·2019-04-03·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543 compat-openssl10: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
CVE-2019-1543 compat-openssl10: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple support
Bugzilla
CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces
bugzilla·2019-04-03·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces
CVE-2019-1543 openssl: ChaCha20-Poly1305 with long nonces
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
Bugzilla
CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
bugzilla·2019-04-03·CVSS 7.4
CVE-2019-1543 [HIGH] CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
CVE-2019-1543 mingw-openssl: openssl: ChaCha20-Poly1305 with long nonces [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects multiple supported
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.htmlhttps://access.redhat.com/errata/RHSA-2019:3700https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=ee22257b1418438ebaf54df98af4e24f494d1809https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=f426625b6ae9a7831010750490a5f0ad689c5ba3https://kc.mcafee.com/corporate/index?page=content&id=SB10365https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/https://seclists.org/bugtraq/2019/Jul/3https://www.debian.org/security/2019/dsa-4475https://www.openssl.org/news/secadv/20190306.txthttps://www.oracle.com/security-alerts/cpuapr2020.htmlhttps://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.htmlhttps://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.htmlhttp://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.htmlhttps://access.redhat.com/errata/RHSA-2019:3700https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=ee22257b1418438ebaf54df98af4e24f494d1809https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=f426625b6ae9a7831010750490a5f0ad689c5ba3https://kc.mcafee.com/corporate/index?page=content&id=SB10365https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/https://seclists.org/bugtraq/2019/Jul/3https://www.debian.org/security/2019/dsa-4475https://www.openssl.org/news/secadv/20190306.txthttps://www.oracle.com/security-alerts/cpuapr2020.htmlhttps://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.htmlhttps://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
2019-03-06
Published