Executive Summary
Informations | |||
---|---|---|---|
Name | CVE-2019-1547 | First vendor Publication | 2019-09-10 |
Vendor | Cve | Last vendor Modification | 2024-11-21 |
Security-Database Scoring CVSS v3
Cvss vector : CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N | |||
---|---|---|---|
Overall CVSS Score | 4.7 | ||
Base Score | 4.7 | Environmental Score | 4.7 |
impact SubScore | 3.6 | Temporal Score | 4.7 |
Exploitabality Sub Score | 1 | ||
Attack Vector | Local | Attack Complexity | High |
Privileges Required | Low | User Interaction | None |
Scope | Unchanged | Confidentiality Impact | High |
Integrity Impact | None | Availability Impact | None |
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : (AV:L/AC:M/Au:N/C:P/I:N/A:N) | |||
---|---|---|---|
Cvss Base Score | 1.9 | Attack Range | Local |
Cvss Impact Score | 2.9 | Attack Complexity | Medium |
Cvss Expoit Score | 3.4 | Authentication | None Required |
Calculate full CVSS 2.0 Vectors scores |
Detail
Normally in OpenSSL EC groups always have a co-factor present and this is used in side channel resistant code paths. However, in some cases, it is possible to construct a group using explicit parameters (instead of using a named curve). In those cases it is possible that such a group does not have the cofactor present. This can occur even where all the parameters match a known named curve. If such a curve is used then OpenSSL falls back to non-side channel resistant code paths which may result in full key recovery during an ECDSA signature operation. In order to be vulnerable an attacker would have to have the ability to time the creation of a large number of signatures where explicit parameters with no co-factor present are in use by an application using libcrypto. For the avoidance of doubt libssl is not vulnerable because explicit parameters are never used. Fixed in OpenSSL 1.1.1d (Affected 1.1.1-1.1.1c). Fixed in OpenSSL 1.1.0l (Affected 1.1.0-1.1.0k). Fixed in OpenSSL 1.0.2t (Affected 1.0.2-1.0.2s). |
Original Source
Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1547 |
CPE : Common Platform Enumeration
Sources (Detail)
Alert History
Date | Informations |
---|---|
2024-11-28 13:27:32 |
|
2024-08-02 13:03:34 |
|
2024-08-02 01:18:21 |
|
2024-06-22 00:27:45 |
|
2024-02-02 02:03:49 |
|
2024-02-01 12:17:15 |
|
2023-11-07 21:39:18 |
|
2023-09-05 12:59:16 |
|
2023-09-05 01:16:57 |
|
2023-09-02 12:58:32 |
|
2023-09-02 01:17:14 |
|
2023-08-12 13:02:27 |
|
2023-08-12 01:16:32 |
|
2023-08-11 12:56:14 |
|
2023-08-11 01:17:00 |
|
2023-08-09 12:49:54 |
|
2023-08-06 12:54:36 |
|
2023-08-06 01:16:26 |
|
2023-08-04 12:54:52 |
|
2023-08-04 01:16:37 |
|
2023-07-14 12:54:51 |
|
2023-07-14 01:16:33 |
|
2023-03-29 01:56:12 |
|
2023-03-28 12:16:51 |
|
2022-10-11 12:48:59 |
|
2022-10-11 01:16:26 |
|
2022-02-08 12:39:19 |
|
2022-02-03 12:39:08 |
|
2021-08-04 21:23:24 |
|
2021-07-31 13:23:01 |
|
2021-07-21 17:24:53 |
|
2021-05-04 13:28:42 |
|
2021-04-22 02:43:11 |
|
2020-10-21 05:22:52 |
|
2020-09-17 21:23:08 |
|
2020-07-22 21:23:03 |
|
2020-07-15 09:22:55 |
|
2020-06-03 21:23:02 |
|
2020-05-23 02:25:23 |
|
2019-10-10 12:11:20 |
|
2019-10-07 12:01:22 |
|
2019-10-03 12:11:01 |
|
2019-10-02 12:01:35 |
|
2019-09-26 12:11:14 |
|
2019-09-25 12:11:07 |
|
2019-09-25 01:10:50 |
|
2019-09-19 21:19:47 |
|
2019-09-12 21:19:59 |
|
2019-09-12 17:19:47 |
|
2019-09-12 05:18:48 |
|
2019-09-10 21:19:51 |
|