CVE-2024-32649 Vulnerability Analysis & Exploit Details

CVE-2024-32649
Vulnerability Scoring

5.3
/10
Significant Risk

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

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-2024-32649 Details

Status: Analyzed

Last updated: 🕥 02 Jan 2025, 22:39 UTC
Originally published on: 🕕 25 Apr 2024, 18:15 UTC

Time between publication and last update: 252 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2024-32649 Vulnerability Summary

CVE-2024-32649: Vyper is a pythonic Smart Contract Language for the Ethereum virtual machine. In versions 0.3.10 and prior, using the `sqrt` builtin can result in double eval vulnerability when the argument has side-effects. It can be seen that the `build_IR` function of the `sqrt` builtin doesn't cache the argument to the stack. As such, it can be evaluated multiple times (instead of retrieving the value from the stack). No vulnerable production contracts were found. Additionally, double evaluation of side-effects should be easily discoverable in client tests. As such, the impact is low. As of time of publication, no fixed versions are available.

Assessing the Risk of CVE-2024-32649

Access Complexity Graph

The exploitability of CVE-2024-32649 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-2024-32649

With low attack complexity and no required privileges, CVE-2024-32649 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-2024-32649, 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-2024-32649, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

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

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

CVE-2024-32649 References

External References

CWE Common Weakness Enumeration

NVD-CWE-Other

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:*:*
  • cpe:2.3:a:vyperlang:vyper:0.3.10:*:*:*:*:python:*:*
    cpe:2.3:a:vyperlang:vyper:0.3.10:*:*:*:*:python:*:*

Protect Your Infrastructure against CVE-2024-32649: 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-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
  • CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
  • CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
  • CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...
  • CVE-2025-2118 – A vulnerability was found in Quantico Tecnologia PRMV 6.48. It has been classified as critical. This affects an unknown part of the file /admin/log...