| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in GnuPG up to 2.2.17. This impacts an unknown function of the component SHA1 Handler. Performing a manipulation as part of Certificate results in risky encryption. This vulnerability is identified as CVE-2019-14855. The attack can be initiated remotely. There is not any exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in GnuPG up to 2.2.17. This affects some unknown processing of the component SHA1 Handler. The manipulation as part of a Certificate leads to a risky encryption vulnerability. CWE is classifying the issue as CWE-327. The product uses a broken or risky cryptographic algorithm or protocol. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
A flaw was found in the way certificate signatures could be forged using collisions found in the SHA-1 algorithm. An attacker could use this weakness to create forged certificate signatures. This issue affects GnuPG versions before 2.2.18.
The weakness was released 03/20/2020 as not defined bug report (Bugzilla). The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2019-14855 since 08/10/2019. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 232212 (Linux Distros Unpatched Vulnerability : CVE-2019-14855), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.2.18 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (232212). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.2VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (Red Hat, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Risky encryptionCWE: CWE-327 / CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 232212
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2019-14855
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: GnuPG 2.2.18
Timeline
08/10/2019 🔍03/20/2020 🔍
03/21/2020 🔍
05/11/2025 🔍
Sources
Advisory: USN-4516-1Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-14855 (🔍)
GCVE (CVE): GCVE-0-2019-14855
GCVE (VulDB): GCVE-100-151941
Entry
Created: 03/21/2020 08:45Updated: 05/11/2025 02:30
Changes: 03/21/2020 08:45 (41), 03/21/2020 08:50 (11), 10/04/2020 04:26 (1), 04/18/2024 13:20 (17), 04/18/2024 13:25 (19), 03/07/2025 05:49 (5), 05/11/2025 02:30 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.