CVE-2023-41052 Vulnerability Analysis & Exploit Details

CVE-2023-41052
Vulnerability Scoring

3.7
/10
Moderate Risk

Exploiting CVE-2023-41052 requires specific conditions, leading to a moderate security impact.

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-41052 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:20 UTC
Originally published on: 🕕 04 Sep 2023, 18:15 UTC

Time between publication and last update: 443 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:N/I:L/A:N

CVE-2023-41052 Vulnerability Summary

CVE-2023-41052: Vyper is a Pythonic Smart Contract Language. In affected versions the order of evaluation of the arguments of the builtin functions `uint256_addmod`, `uint256_mulmod`, `ecadd` and `ecmul` does not follow source order. This behaviour is problematic when the evaluation of one of the arguments produces side effects that other arguments depend on. A patch is currently being developed on pull request #3583. When using builtins from the list above, users should make sure that the arguments of the expression do not produce side effects or, if one does, that no other argument is dependent on those side effects.

Assessing the Risk of CVE-2023-41052

Access Complexity Graph

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

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

  • Confidentiality: None
    CVE-2023-41052 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2023-41052 may cause minor changes to data without severely impacting its accuracy.
  • Availability: None
    CVE-2023-41052 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.067% (probability of exploit)

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

CVE-2023-41052 References

External References

CWE Common Weakness Enumeration

CWE-670

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-41052: 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-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...
  • CVE-2025-2125 – A vulnerability has been found in Control iD RH iD 25.2.25.0 and classified as problematic. This vulnerability affects unknown code of the file /v2...
  • CVE-2025-2124 – A vulnerability, which was classified as problematic, was found in Control iD RH iD 25.2.25.0. This affects an unknown part of the file /v2/custome...