CVE-2018-1000022 Vulnerability Analysis & Exploit Details

CVE-2018-1000022
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2018-1000022 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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: Required
    User interaction is necessary for successful exploitation.

CVE-2018-1000022 Details

Status: Modified

Last updated: 🕞 21 Nov 2024, 03:39 UTC
Originally published on: 🕚 09 Feb 2018, 23:29 UTC

Time between publication and last update: 2476 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

CVE-2018-1000022 Vulnerability Summary

CVE-2018-1000022: Electrum Technologies GmbH Electrum Bitcoin Wallet version prior to version 3.0.5 contains a Missing Authorization vulnerability in JSONRPC interface that can result in Bitcoin theft, if the user's wallet is not password protected. This attack appear to be exploitable via The victim must visit a web page with specially crafted javascript. This vulnerability appears to have been fixed in 3.0.5.

Assessing the Risk of CVE-2018-1000022

Access Complexity Graph

The exploitability of CVE-2018-1000022 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-2018-1000022

CVE-2018-1000022 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-2018-1000022, 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-2018-1000022, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2018-1000022 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2018-1000022 poses no threat to data integrity.
  • Availability: None
    CVE-2018-1000022 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.168% (probability of exploit)

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

CVE-2018-1000022 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:electrum:bitcoin_wallet:-:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:-:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.8:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.8:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.5:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.6:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.6:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.7:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.7:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:1.9.8:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:1.9.8:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.0:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.0.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.1.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.1.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.3.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.3.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.3.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.3.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.3.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.3.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.4.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.4.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.4.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.4.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.5:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.5.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.5.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.5.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.5.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.6:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.4:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.5:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.5:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.6:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.6:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.7:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.7:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.8:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.8:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.9:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.9:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.10:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.10:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.11:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.11:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.12:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.12:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.13:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.13:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.14:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.14:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.15:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.15:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.16:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.16:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.17:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.17:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.7.18:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.7.18:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:2.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:2.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:3.0:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:3.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:3.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:3.0.2:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:3.0.2:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:3.0.3:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:3.0.3:*:*:*:*:*:*:*
  • cpe:2.3:a:electrum:bitcoin_wallet:3.0.4:*:*:*:*:*:*:*
    cpe:2.3:a:electrum:bitcoin_wallet:3.0.4:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2018-1000022: 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-2025-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
  • CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...
  • CVE-2025-3798 – A vulnerability, which was classified as critical, has been found in WCMS 11. This issue affects the function sub of the file app/admin/AdvadminCon...
  • CVE-2025-3661 – The SB Chart block plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘className’ parameter in all versions up to, and inclu...
  • CVE-2025-3404 – The Download Manager plugin for WordPress is vulnerable to arbitrary file deletion due to insufficient file path validation in the savePackage func...