CVE-2023-34459 Vulnerability Analysis & Exploit Details

CVE-2023-34459
Vulnerability Scoring

5.3
/10
Significant Risk

Security assessments indicate that CVE-2023-34459 presents a notable risk, potentially requiring prompt 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: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2023-34459 Details

Status: Modified

Last updated: 🕗 21 Nov 2024, 08:07 UTC
Originally published on: 🕚 16 Jun 2023, 23:15 UTC

Time between publication and last update: 523 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-34459 Vulnerability Summary

CVE-2023-34459: OpenZeppelin Contracts is a library for smart contract development. Starting in version 4.7.0 and prior to version 4.9.2, when the `verifyMultiProof`, `verifyMultiProofCalldata`, `procesprocessMultiProof`, or `processMultiProofCalldat` functions are in use, it is possible to construct merkle trees that allow forging a valid multiproof for an arbitrary set of leaves. A contract may be vulnerable if it uses multiproofs for verification and the merkle tree that is processed includes a node with value 0 at depth 1 (just under the root). This could happen inadvertedly for balanced trees with 3 leaves or less, if the leaves are not hashed. This could happen deliberately if a malicious tree builder includes such a node in the tree. A contract is not vulnerable if it uses single-leaf proving (`verify`, `verifyCalldata`, `processProof`, or `processProofCalldata`), or if it uses multiproofs with a known tree that has hashed leaves. Standard merkle trees produced or validated with the @openzeppelin/merkle-tree library are safe. The problem has been patched in version 4.9.2. Some workarounds are available. For those using multiproofs: When constructing merkle trees hash the leaves and do not insert empty nodes in your trees. Using the @openzeppelin/merkle-tree package eliminates this issue. Do not accept user-provided merkle roots without reconstructing at least the first level of the tree. Verify the merkle tree structure by reconstructing it from the leaves.

Assessing the Risk of CVE-2023-34459

Access Complexity Graph

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

This vulnerability, CVE-2023-34459, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

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

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

CVE-2023-34459 References

External References

CWE Common Weakness Enumeration

CWE-354

CAPEC Common Attack Pattern Enumeration and Classification

  • Checksum Spoofing CAPEC-145 An adversary spoofs a checksum message for the purpose of making a payload appear to have a valid corresponding checksum. Checksums are used to verify message integrity. They consist of some value based on the value of the message they are protecting. Hash codes are a common checksum mechanism. Both the sender and recipient are able to compute the checksum based on the contents of the message. If the message contents change between the sender and recipient, the sender and recipient will compute different checksum values. Since the sender's checksum value is transmitted with the message, the recipient would know that a modification occurred. In checksum spoofing an adversary modifies the message body and then modifies the corresponding checksum so that the recipient's checksum calculation will match the checksum (created by the adversary) in the message. This would prevent the recipient from realizing that a change occurred.
  • Padding Oracle Crypto Attack CAPEC-463 An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key.
  • Manipulating Writeable Configuration Files CAPEC-75 Generally these are manually edited files that are not in the preview of the system administrators, any ability on the attackers' behalf to modify these files, for example in a CVS repository, gives unauthorized access directly to the application, the same as authorized users.

Vulnerable Configurations

  • cpe:2.3:a:openzeppelin:contracts:4.7.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.7.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.0:rc2:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.0:rc2:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.9.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.9.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.9.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.9.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.9.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.9.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts:4.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts:4.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.7.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc2:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.0:rc2:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.8.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:rc0:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:rc0:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:rc1:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.0:rc1:*:*:*:node.js:*:*
  • cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:openzeppelin:contracts_upgradeable:4.9.1:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2023-34459: 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...