Executive Summary



This Alert is flagged as TOP 25 Common Weakness Enumeration from CWE/SANS. For more information, you can read this.
Informations
Name CVE-2019-1543 First vendor Publication 2019-03-06
Vendor Cve Last vendor Modification 2023-11-07

Security-Database Scoring CVSS v3

Cvss vector : CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Overall CVSS Score 7.4
Base Score 7.4 Environmental Score 7.4
impact SubScore 5.2 Temporal Score 7.4
Exploitabality Sub Score 2.2
 
Attack Vector Network Attack Complexity High
Privileges Required None User Interaction None
Scope Unchanged Confidentiality Impact High
Integrity Impact High Availability Impact None
Calculate full CVSS 3.0 Vectors scores

Security-Database Scoring CVSS v2

Cvss vector : (AV:N/AC:M/Au:N/C:P/I:P/A:N)
Cvss Base Score 5.8 Attack Range Network
Cvss Impact Score 4.9 Attack Complexity Medium
Cvss Expoit Score 8.6 Authentication None Required
Calculate full CVSS 2.0 Vectors scores

Detail

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

Original Source

Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1543

CWE : Common Weakness Enumeration

% Id Name
50 % CWE-330 Use of Insufficiently Random Values
50 % CWE-327 Use of a Broken or Risky Cryptographic Algorithm (CWE/SANS Top 25)

CPE : Common Platform Enumeration

TypeDescriptionCount
Application 392

Sources (Detail)

https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=ee22257b1418...
https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=f426625b6ae9...
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedora...
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedora...
Source Url
BUGTRAQ https://seclists.org/bugtraq/2019/Jul/3
CONFIRM https://kc.mcafee.com/corporate/index?page=content&id=SB10365
https://www.openssl.org/news/secadv/20190306.txt
DEBIAN https://www.debian.org/security/2019/dsa-4475
MISC https://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html
https://www.oracle.com/technetwork/security-advisory/cpuoct2019-5072832.html
N/A https://www.oracle.com/security-alerts/cpuapr2020.html
REDHAT https://access.redhat.com/errata/RHSA-2019:3700
SUSE http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00056.html

Alert History

If you want to see full details history, please login or register.
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Date Informations
2024-02-02 02:03:47
  • Multiple Updates
2024-02-01 12:17:15
  • Multiple Updates
2023-11-07 21:40:19
  • Multiple Updates
2023-09-05 12:59:16
  • Multiple Updates
2023-09-05 01:16:57
  • Multiple Updates
2023-09-02 12:58:32
  • Multiple Updates
2023-09-02 01:17:14
  • Multiple Updates
2023-08-12 13:02:27
  • Multiple Updates
2023-08-12 01:16:32
  • Multiple Updates
2023-08-11 12:56:14
  • Multiple Updates
2023-08-11 01:17:00
  • Multiple Updates
2023-08-09 12:49:54
  • Multiple Updates
2023-08-06 12:54:35
  • Multiple Updates
2023-08-06 01:16:26
  • Multiple Updates
2023-08-04 12:54:52
  • Multiple Updates
2023-08-04 01:16:37
  • Multiple Updates
2023-07-14 12:54:51
  • Multiple Updates
2023-07-14 01:16:33
  • Multiple Updates
2023-03-29 01:56:12
  • Multiple Updates
2023-03-28 12:16:51
  • Multiple Updates
2022-10-11 12:48:59
  • Multiple Updates
2022-10-11 01:16:26
  • Multiple Updates
2022-02-08 12:39:19
  • Multiple Updates
2022-02-03 12:39:08
  • Multiple Updates
2021-08-04 21:23:25
  • Multiple Updates
2021-07-31 13:23:01
  • Multiple Updates
2021-07-21 17:25:07
  • Multiple Updates
2021-05-04 13:23:06
  • Multiple Updates
2021-04-22 02:38:03
  • Multiple Updates
2020-05-23 02:25:22
  • Multiple Updates
2019-09-26 12:11:14
  • Multiple Updates
2019-09-25 12:11:07
  • Multiple Updates
2019-07-31 12:10:41
  • Multiple Updates
2019-07-24 12:05:10
  • Multiple Updates
2019-07-03 12:10:25
  • Multiple Updates
2019-07-02 15:40:06
  • Multiple Updates
2019-06-04 05:19:25
  • Multiple Updates
2019-05-27 17:19:22
  • Multiple Updates
2019-04-05 05:18:46
  • Multiple Updates
2019-03-15 17:19:16
  • Multiple Updates
2019-03-15 13:19:27
  • Multiple Updates
2019-03-12 13:19:07
  • Multiple Updates
2019-03-11 17:19:31
  • Multiple Updates
2019-03-07 00:19:04
  • First insertion