{"id":"EUVD-2023-1907","enisaUuid":"b0e2f754-a8a1-3a20-9560-3f06e8c31255","description":"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.\n\nA 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.\n\nA 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.\n\nThe problem has been patched in version 4.9.2.\n\nSome 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.","datePublished":"Jun 16, 2023, 10:13:18 PM","dateUpdated":"Dec 16, 2024, 6:35:27 PM","baseScore":5.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","references":"https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wprv-93r4-jj2p\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/commit/4d2383e17186be3e8ccf5a442e9686ecc7de1c55\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.9.2\n","aliases":"CVE-2023-34459\nGHSA-wprv-93r4-jj2p\n","assigner":"GitHub_M","epss":0.37,"enisaIdProduct":[{"id":"551a743b-c853-3b7d-a9f7-f4ff47b49c22","product":{"name":"openzeppelin-contracts","vendor":{"name":"OpenZeppelin"}},"product_version":"4.7.0, \u003c 4.9.2"}],"enisaIdVendor":[{"id":"320d57ef-449b-3d2a-aa17-b7514011d6be","vendor":{"name":"OpenZeppelin"}}],"enisaIdVulnerability":[{"id":"4938d850-fee0-3d47-a877-d5db2a3e59ec","vulnerability":{"id":"CVE-2023-34459","description":"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.\n\nA 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.\n\nA 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.\n\nThe problem has been patched in version 4.9.2.\n\nSome 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.","datePublished":"Jun 16, 2023, 10:13:18 PM","dateUpdated":"Dec 16, 2024, 6:35:27 PM","status":"PUBLISHED","baseScore":5.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","references":"https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wprv-93r4-jj2p\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/commit/4d2383e17186be3e8ccf5a442e9686ecc7de1c55\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.9.2\n","enisa_id":"EUVD-2023-1907\n","assigner":"GitHub_M","epss":0.37,"dataProcessed":"Nov 15, 2026, 7:21:23 AM","vulnerabilityProduct":[{"id":"fd037e79-200d-3e7f-85db-4911bab59bcb","product":{"name":"openzeppelin-contracts","vendor":{"name":"OpenZeppelin"}},"product_version":"4.7.0, \u003c 4.9.2"}],"vulnerabilityVendor":[{"id":"e4c40afb-11f8-3e7a-a688-13ba2e078706","vendor":{"name":"OpenZeppelin"}}]}},{"id":"7504ba3a-708f-32c0-b951-8129b78cfbfc","vulnerability":{"id":"GHSA-wprv-93r4-jj2p","description":"OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees","datePublished":"Jun 19, 2023, 7:46:37 PM","dateUpdated":"Jun 19, 2023, 7:46:37 PM","baseScore":null,"references":"https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wprv-93r4-jj2p\nhttps://nvd.nist.gov/vuln/detail/CVE-2023-34459\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/commit/4d2383e17186be3e8ccf5a442e9686ecc7de1c55\nhttps://github.com/OpenZeppelin/openzeppelin-contracts\nhttps://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.9.2\n","enisa_id":"EUVD-2023-1907\n","aliases":"GHSA-wprv-93r4-jj2p\nCVE-2023-34459\n","epss":0.0,"dataProcessed":"Nov 15, 2026, 2:32:34 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}}],"enisaIdAdvisory":[]}