CVE-2022-25893 Vulnerability Analysis & Exploit Details

CVE-2022-25893
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2022-25893 has severe implications, demanding immediate intervention.

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-2022-25893 Details

Status: Modified

Last updated: 🕗 15 Apr 2025, 20:15 UTC
Originally published on: 🕔 21 Dec 2022, 05:15 UTC

Time between publication and last update: 846 days

CVSS Release: version 3

CVSS3 Source

report@snyk.io

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-25893 Vulnerability Summary

CVE-2022-25893: The package vm2 before 3.9.10 are vulnerable to Arbitrary Code Execution due to the usage of prototype lookup for the WeakMap.prototype.set method. Exploiting this vulnerability leads to access to a host object and a sandbox compromise.

Assessing the Risk of CVE-2022-25893

Access Complexity Graph

The exploitability of CVE-2022-25893 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-2022-25893

With low attack complexity and no required privileges, CVE-2022-25893 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-2022-25893, 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-2022-25893, 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-2022-25893 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-25893 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-25893 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.476% (probability of exploit)

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

CVE-2022-25893 References

External References

CWE Common Weakness Enumeration

CWE-471

CAPEC Common Attack Pattern Enumeration and Classification

  • Application API Message Manipulation via Man-in-the-Middle CAPEC-384 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the content of messages. Performing this attack can allow the attacker to gain unauthorized privileges within the application, or conduct attacks such as phishing, deceptive strategies to spread malware, or traditional web-application attacks. The techniques require use of specialized software that allow the attacker to perform adversary-in-the-middle (CAPEC-94) communications between the web browser and the remote system. Despite the use of AiTH software, the attack is actually directed at the server, as the client is one node in a series of content brokers that pass information along to the application framework. Additionally, it is not true "Adversary-in-the-Middle" attack at the network layer, but an application-layer attack the root cause of which is the master applications trust in the integrity of code supplied by the client.
  • Transaction or Event Tampering via Application API Manipulation CAPEC-385 An attacker hosts or joins an event or transaction within an application framework in order to change the content of messages or items that are being exchanged. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that look authentic but may contain deceptive links, substitute one item or another, spoof an existing item and conduct a false exchange, or otherwise change the amounts or identity of what is being exchanged. The techniques require use of specialized software that allow the attacker to man-in-the-middle communications between the web browser and the remote system in order to change the content of various application elements. Often, items exchanged in game can be monetized via sales for coin, virtual dollars, etc. The purpose of the attack is for the attack to scam the victim by trapping the data packets involved the exchange and altering the integrity of the transfer process.
  • Application API Navigation Remapping CAPEC-386 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of links/buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains links/buttons that point to an attacker controlled destination. Some applications make navigation remapping more difficult to detect because the actual HREF values of images, profile elements, and links/buttons are masked. One example would be to place an image in a user's photo gallery that when clicked upon redirected the user to an off-site location. Also, traditional web vulnerabilities (such as CSRF) can be constructed with remapped buttons or links. In some cases navigation remapping can be used for Phishing attacks or even means to artificially boost the page view, user site reputation, or click-fraud.
  • Navigation Remapping To Propagate Malicious Content CAPEC-387 An adversary manipulates either egress or ingress data from a client within an application framework in order to change the content of messages and thereby circumvent the expected application logic.
  • Application API Button Hijacking CAPEC-388 An attacker manipulates either egress or ingress data from a client within an application framework in order to change the destination and/or content of buttons displayed to a user within API messages. Performing this attack allows the attacker to manipulate content in such a way as to produce messages or content that looks authentic but contains buttons that point to an attacker controlled destination.

Vulnerable Configurations

  • cpe:2.3:a:vm2_project:vm2:-:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:-:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:0.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:0.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:2.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:2.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.4.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.4.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.6.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.6.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.8.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.8.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vm2_project:vm2:3.9.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:vm2_project:vm2:3.9.9:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2022-25893: 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-43903 – NSSCryptoSignBackend.cc in Poppler before 25.04.0 does not verify the adbe.pkcs7.sha1 signatures on documents, resulting in potential signature forgeries.
  • CVE-2025-3796 – A vulnerability classified as critical has been found in PHPGurukul Men Salon Management System 1.0. This affects an unknown part of the file /admi...
  • CVE-2025-32953 – z80pack is a mature emulator of multiple platforms with 8080 and Z80 CPU. In version 1.38 and prior, the `makefile-ubuntu.yml` workflow file uses `...
  • CVE-2025-29058 – An issue in Qimou CMS v.3.34.0 allows a remote attacker to execute arbitrary code via the upgrade.php component.
  • CVE-2024-53591 – An issue in the login page of Seclore v3.27.5.0 allows attackers to bypass authentication via a brute force attack.