CVE-2023-42443 Vulnerability Analysis & Exploit Details

CVE-2023-42443
Vulnerability Scoring

8.1
/10
Severe Risk

Cybersecurity professionals consider CVE-2023-42443 an immediate threat requiring urgent 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: None
    No user interaction is necessary for exploitation.

CVE-2023-42443 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:22 UTC
Originally published on: 🕘 18 Sep 2023, 21:16 UTC

Time between publication and last update: 429 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-42443 Vulnerability Summary

CVE-2023-42443: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). In version 0.3.9 and prior, under certain conditions, the memory used by the builtins `raw_call`, `create_from_blueprint` and `create_copy_of` can be corrupted. For `raw_call`, the argument buffer of the call can be corrupted, leading to incorrect `calldata` in the sub-context. For `create_from_blueprint` and `create_copy_of`, the buffer for the to-be-deployed bytecode can be corrupted, leading to deploying incorrect bytecode. Each builtin has conditions that must be fulfilled for the corruption to happen. For `raw_call`, the `data` argument of the builtin must be `msg.data` and the `value` or `gas` passed to the builtin must be some complex expression that results in writing to the memory. For `create_copy_of`, the `value` or `salt` passed to the builtin must be some complex expression that results in writing to the memory. For `create_from_blueprint`, either no constructor parameters should be passed to the builtin or `raw_args` should be set to True, and the `value` or `salt` passed to the builtin must be some complex expression that results in writing to the memory. As of time of publication, no patched version exists. The issue is still being investigated, and there might be other cases where the corruption might happen. When the builtin is being called from an `internal` function `F`, the issue is not present provided that the function calling `F` wrote to memory before calling `F`. As a workaround, the complex expressions that are being passed as kwargs to the builtin should be cached in memory prior to the call to the builtin.

Assessing the Risk of CVE-2023-42443

Access Complexity Graph

The exploitability of CVE-2023-42443 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-2023-42443

CVE-2023-42443 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-2023-42443, 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-2023-42443, 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-2023-42443 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-42443 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2023-42443 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.19% (probability of exploit)

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

CVE-2023-42443 References

External References

CWE Common Weakness Enumeration

CWE-787

Vulnerable Configurations

  • cpe:2.3:a:vyperlang:vyper:0.0.4:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.0.4:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta1:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta1:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta2:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta2:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta3:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta3:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta4:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta4:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta5:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta5:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta6:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta6:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta7:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta7:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta8:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta8:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta9:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta9:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta10:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta10:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta11:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta11:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta12:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta12:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta13:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta13:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta14:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta14:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta15:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta15:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta16:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta16:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.1.0:beta17:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.1.0:beta17:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.0:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.0:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.1:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.1:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.2:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.2:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.3:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.3:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.4:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.4:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.5:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.5:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.6:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.6:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.7:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.7:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.8:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.8:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.9:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.9:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.10:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.10:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.11:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.11:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.12:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.12:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.13:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.13:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.14:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.14:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.15:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.15:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.2.16:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.2.16:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.0:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.0:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.1:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.1:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.2:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.2:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.3:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.3:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.4:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.4:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.5:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.5:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.6:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.6:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.7:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.7:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.8:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.8:*:*:*:*:python:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.9:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.9:*:*:*:*:python:*:*

Protect Your Infrastructure against CVE-2023-42443: 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-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...