CVE-2019-1543
OpenSSL ChaCha20-Poly1305 Nonce Length Vulnerability
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).
INFO
Published Date :
March 6, 2019, 9:29 p.m.
Last Modified :
Nov. 7, 2023, 3:08 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
5.2
Exploitability Score :
2.2
Public PoC/Exploit Available at Github
CVE-2019-1543 has a 29 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2019-1543.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
None
Shell Smarty
None
Shell Go Smarty Dockerfile Open Policy Agent Mustache Makefile
None
Shell Go Makefile Smarty Dockerfile Open Policy Agent Mustache
None
Dockerfile Shell Go Smarty Open Policy Agent Mustache Makefile
None
Smarty
Demo repository showcasing some of the possibilities of Aqua Trivy.
cncf-demo trivy
Dockerfile Shell
https://github.com/aquasecurity/trivy
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
None
None
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
None
A security framework by Aquasecurity
None
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
None
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
None
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
None
Dockerfile Makefile Shell Go Smarty Open Policy Agent Mustache
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2019-1543 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2019-1543 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Added Reference OpenSSL Software Foundation https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=f426625b6ae9a7831010750490a5f0ad689c5ba3 [No types assigned] Added Reference OpenSSL Software Foundation https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=ee22257b1418438ebaf54df98af4e24f494d1809 [No types assigned] Added Reference OpenSSL Software Foundation https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/ [No types assigned] Added Reference OpenSSL Software Foundation https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/ [No types assigned] Removed Reference OpenSSL Software Foundation https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=f426625b6ae9a7831010750490a5f0ad689c5ba3 Removed Reference OpenSSL Software Foundation https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ee22257b1418438ebaf54df98af4e24f494d1809 Removed Reference OpenSSL Software Foundation https://lists.fedoraproject.org/archives/list/[email protected]/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/ Removed Reference OpenSSL Software Foundation https://lists.fedoraproject.org/archives/list/[email protected]/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/ -
CVE Modified by [email protected]
Jul. 31, 2021
Action Type Old Value New Value Added Reference https://kc.mcafee.com/corporate/index?page=content&id=SB10365 [No Types Assigned] -
CWE Remap by [email protected]
Jul. 21, 2021
Action Type Old Value New Value Changed CWE CWE-310 CWE-327 CWE-330 -
CVE Modified by [email protected]
Apr. 15, 2020
Action Type Old Value New Value Added Reference https://www.oracle.com/security-alerts/cpuapr2020.html [No Types Assigned] -
CVE Modified by [email protected]
Nov. 06, 2019
Action Type Old Value New Value Added Reference https://access.redhat.com/errata/RHSA-2019:3700 [No Types Assigned] -
CVE Modified by [email protected]
Oct. 16, 2019
Action Type Old Value New Value Added Reference https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html [No Types Assigned] -
CVE Modified by [email protected]
Sep. 26, 2019
Action Type Old Value New Value Added Reference https://lists.fedoraproject.org/archives/list/[email protected]/message/Y3IVFGSERAZLNJCK35TEM2R4726XIH3Z/ [No Types Assigned] -
CVE Modified by [email protected]
Sep. 25, 2019
Action Type Old Value New Value Added Reference https://lists.fedoraproject.org/archives/list/[email protected]/message/ZBEV5QGDRFUZDMNECFXUSN5FMYOZDE4V/ [No Types Assigned] -
CVE Modified by [email protected]
Jul. 30, 2019
Action Type Old Value New Value Added Reference http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.html [No Types Assigned] -
CVE Modified by [email protected]
Jul. 23, 2019
Action Type Old Value New Value Added Reference https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html [No Types Assigned] -
CVE Modified by [email protected]
Jul. 02, 2019
Action Type Old Value New Value Added Reference https://www.debian.org/security/2019/dsa-4475 [No Types Assigned] -
CVE Modified by [email protected]
Jul. 02, 2019
Action Type Old Value New Value Added Reference https://seclists.org/bugtraq/2019/Jul/3 [No Types Assigned] -
CVE Modified by [email protected]
Jun. 03, 2019
Action Type Old Value New Value Changed 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-dev (Affected 1.1.1-1.1.1b). Fixed in OpenSSL 1.1.0k-dev (Affected 1.1.0-1.1.0j). 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). Removed Reference https://support.f5.com/csp/article/K51303334 [No Types Assigned] Removed Reference http://www.securityfocus.com/bid/107349 [Third Party Advisory, VDB Entry] Removed Reference https://security.netapp.com/advisory/ntap-20190314-0002/ [Third Party Advisory] Removed Reference http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00027.html [No Types Assigned] -
CVE Modified by [email protected]
May. 27, 2019
Action Type Old Value New Value Added Reference https://support.f5.com/csp/article/K51303334 [No Types Assigned] -
CVE Modified by [email protected]
Apr. 04, 2019
Action Type Old Value New Value Added Reference http://lists.opensuse.org/opensuse-security-announce/2019-04/msg00027.html [No Types Assigned] -
Modified Analysis by [email protected]
Mar. 15, 2019
Action Type Old Value New Value Changed Reference Type http://www.securityfocus.com/bid/107349 No Types Assigned http://www.securityfocus.com/bid/107349 Third Party Advisory, VDB Entry Changed Reference Type https://security.netapp.com/advisory/ntap-20190314-0002/ No Types Assigned https://security.netapp.com/advisory/ntap-20190314-0002/ Third Party Advisory -
CVE Modified by [email protected]
Mar. 15, 2019
Action Type Old Value New Value Added Reference https://security.netapp.com/advisory/ntap-20190314-0002/ [No Types Assigned] -
CVE Modified by [email protected]
Mar. 12, 2019
Action Type Old Value New Value Added Reference http://www.securityfocus.com/bid/107349 [No Types Assigned] -
Initial Analysis by [email protected]
Mar. 11, 2019
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:M/Au:N/C:P/I:P/A:N) Added CVSS V3 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Changed Reference Type https://www.openssl.org/news/secadv/20190306.txt No Types Assigned https://www.openssl.org/news/secadv/20190306.txt Vendor Advisory Changed Reference Type https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ee22257b1418438ebaf54df98af4e24f494d1809 No Types Assigned https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=ee22257b1418438ebaf54df98af4e24f494d1809 Mailing List, Patch, Vendor Advisory Changed Reference Type https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=f426625b6ae9a7831010750490a5f0ad689c5ba3 No Types Assigned https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff;h=f426625b6ae9a7831010750490a5f0ad689c5ba3 Mailing List, Patch, Vendor Advisory Added CWE CWE-310 Added CPE Configuration OR *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 1.1.0 up to (including) 1.1.0j *cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 1.1.1 up to (including) 1.1.1b
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2019-1543 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2019-1543
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
3.38 }} 0.88%
score
0.91590
percentile