CVE-2019-18672 Vulnerability Analysis & Exploit Details

CVE-2019-18672
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2019-18672 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2019-18672 Details

Status: Modified

Last updated: 🕟 21 Nov 2024, 04:33 UTC
Originally published on: 🕕 06 Dec 2019, 18:15 UTC

Time between publication and last update: 1811 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

CVE-2019-18672 Vulnerability Summary

CVE-2019-18672: Insufficient checks in the finite state machine of the ShapeShift KeepKey hardware wallet before firmware 6.2.2 allow a partial reset of cryptographic secrets to known values via crafted messages. Notably, this breaks the security of U2F for new server registrations and invalidates existing registrations. This vulnerability can be exploited by unauthenticated attackers and the interface is reachable via WebUSB.

Assessing the Risk of CVE-2019-18672

Access Complexity Graph

The exploitability of CVE-2019-18672 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2019-18672

With low attack complexity and no required privileges, CVE-2019-18672 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2019-18672, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2019-18672, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2019-18672 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2019-18672 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2019-18672 does not impact system availability.

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.251% (probability of exploit)

EPSS Percentile: 64.83% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 35.17% of others.

CVE-2019-18672 References

External References

CWE Common Weakness Enumeration

CWE-354

CAPEC Common Attack Pattern Enumeration and Classification

  • Checksum Spoofing CAPEC-145 An adversary spoofs a checksum message for the purpose of making a payload appear to have a valid corresponding checksum. Checksums are used to verify message integrity. They consist of some value based on the value of the message they are protecting. Hash codes are a common checksum mechanism. Both the sender and recipient are able to compute the checksum based on the contents of the message. If the message contents change between the sender and recipient, the sender and recipient will compute different checksum values. Since the sender's checksum value is transmitted with the message, the recipient would know that a modification occurred. In checksum spoofing an adversary modifies the message body and then modifies the corresponding checksum so that the recipient's checksum calculation will match the checksum (created by the adversary) in the message. This would prevent the recipient from realizing that a change occurred.
  • Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.

Vulnerable Configurations

  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.0:-:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.0:-:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:-:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:-:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:rc:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:rc:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:rc1:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:1.2.0:rc1:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:2.0.9:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:2.0.9:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:2.0.11:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:2.0.11:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:2.0.12:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:2.0.12:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:2.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:2.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:2.2.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:2.2.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.5:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.5:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.6:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.6:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.7:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.7:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.8:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.8:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.9:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.9:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.10:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.10:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.12:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.12:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.14:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.14:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.15:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.15:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.16:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.16:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.17:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.17:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.0.18:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.0.18:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:3.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:3.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:4.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:4.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:4.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:4.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:4.0.3:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:4.0.3:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.1.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.1.2:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.1.2:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.2.2:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.2.2:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.2.4:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.2.4:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.3.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.3.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.4.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.4.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.5.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.5.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.6.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.6.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.7.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.7.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.8.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.8.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.8.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.8.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.9.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.9.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.9.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.9.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.10.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.10.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.10.2:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.10.2:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:5.11.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:5.11.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.0.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.0.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.0.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.0.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.0.2:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.0.2:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.0.4:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.0.4:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.1.0:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.1.0:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.1.1:*:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.1.1:*:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.2.0:-:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.2.0:-:*:*:*:*:*:*
  • cpe:2.3:o:shapeshift:keepkey_firmware:6.2.0:hotfix0:*:*:*:*:*:*
    cpe:2.3:o:shapeshift:keepkey_firmware:6.2.0:hotfix0:*:*:*:*:*:*
  • cpe:2.3:h:shapeshift:keepkey_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:h:shapeshift:keepkey_firmware:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2019-18672: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...