CVE-2024-24563 Vulnerability Analysis & Exploit Details

CVE-2024-24563
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2024-24563 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-2024-24563 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:59 UTC
Originally published on: 🕔 07 Feb 2024, 17:15 UTC

Time between publication and last update: 287 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:H/I:H/A:H

CVE-2024-24563 Vulnerability Summary

CVE-2024-24563: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine. Arrays can be keyed by a signed integer, while they are defined for unsigned integers only. The typechecker doesn't throw when spotting the usage of an `int` as an index for an array. The typechecker allows the usage of signed integers to be used as indexes to arrays. The vulnerability is present in different forms in all versions, including `0.3.10`. For ints, the 2's complement representation is used. Because the array was declared very large, the bounds checking will pass Negative values will simply be represented as very large numbers. As of time of publication, a fixed version does not exist. There are three potential vulnerability classes: unpredictable behavior, accessing inaccessible elements and denial of service. Class 1: If it is possible to index an array with a negative integer without reverting, this is most likely not anticipated by the developer and such accesses can cause unpredictable behavior for the contract. Class 2: If a contract has an invariant in the form `assert index < x`, the developer will suppose that no elements on indexes `y | y >= x` are accessible. However, by using negative indexes, this can be bypassed. Class 3: If the index is dependent on the state of the contract, this poses a risk of denial of service. If the state of the contract can be manipulated in such way that the index will be forced to be negative, the array access can always revert (because most likely the array won't be declared extremely large). However, all these the scenarios are highly unlikely. Most likely behavior is a revert on the bounds check.

Assessing the Risk of CVE-2024-24563

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2024-24563 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-24563, 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-24563, 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-2024-24563 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2024-24563 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2024-24563 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.12% (probability of exploit)

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

CVE-2024-24563 References

External References

CWE Common Weakness Enumeration

CWE-129

CAPEC Common Attack Pattern Enumeration and Classification

  • Overflow Buffers CAPEC-100 Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an adversary. As a consequence, an adversary is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the adversaries' choice.

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-24563: 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...