CVE-2023-46247 Vulnerability Analysis & Exploit Details

CVE-2023-46247
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2023-46247 poses a critical security risk that could lead to severe breaches.

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-2023-46247 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:28 UTC
Originally published on: 🕗 13 Dec 2023, 20:15 UTC

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

CVE-2023-46247 Vulnerability Summary

CVE-2023-46247: Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). Contracts containing large arrays might underallocate the number of slots they need by 1. Prior to v0.3.8, the calculation to determine how many slots a storage variable needed used `math.ceil(type_.size_in_bytes / 32)`. The intermediate floating point step can produce a rounding error if there are enough bits set in the IEEE-754 mantissa. Roughly speaking, if `type_.size_in_bytes` is large (> 2**46), and slightly less than a power of 2, the calculation can overestimate how many slots are needed by 1. If `type_.size_in_bytes` is slightly more than a power of 2, the calculation can underestimate how many slots are needed by 1. This issue is patched in version 0.3.8.

Assessing the Risk of CVE-2023-46247

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2023-46247 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-2023-46247, 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-46247, 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-46247 has no significant impact on data confidentiality.
  • Integrity: High
    CVE-2023-46247 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2023-46247 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.089% (probability of exploit)

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

CVE-2023-46247 References

External References

CWE Common Weakness Enumeration

CWE-682

CAPEC Common Attack Pattern Enumeration and Classification

  • Integer Attacks CAPEC-128 An attacker takes advantage of the structure of integer variables to cause these variables to assume values that are not expected by an application. For example, adding one to the largest positive integer in a signed integer variable results in a negative number. Negative numbers may be illegal in an application and the application may prevent an attacker from providing them directly, but the application may not consider that adding two positive numbers can create a negative number do to the structure of integer storage formats.
  • Pointer Manipulation CAPEC-129 This attack pattern involves an adversary manipulating a pointer within a target application resulting in the application accessing an unintended memory location. This can result in the crashing of the application or, for certain pointer values, access to data that would not normally be possible or the execution of arbitrary code. Since pointers are simply integer variables, Integer Attacks may often be used in Pointer Attacks.

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:*:*

Protect Your Infrastructure against CVE-2023-46247: 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-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...
  • CVE-2025-3278 – The UrbanGo Membership plugin for WordPress is vulnerable to privilege escalation in versions up to, and including, 1.0.4. This is due to the plugi...
  • CVE-2025-2010 – The JobWP – Job Board, Job Listing, Career Page and Recruitment Plugin plugin for WordPress is vulnerable to SQL Injection via the 'jobwp_upload_re...
  • 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...