CVE-2023-34459
published 2023-06-16CVE-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`…
PriorityP431medium5.9CVSS 3.1
AVNACHPRNUINSUCNIHAN
EPSS
0.37%
29.3th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| openzeppelin | contracts | >= 4.7.0 < 4.9.2 | 4.9.2 |
| openzeppelin | contracts | >= 4.7.0 < 4.9.2 | 4.9.2 |
| openzeppelin | contracts-upgradeable | >= 4.7.0 < 4.9.2 | 4.9.2 |
| openzeppelin | contracts_upgradeable | >= 4.7.0 < 4.9.2 | 4.9.2 |
| openzeppelin | openzeppelin-contracts | — | — |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
osv·2023-06-19
CVE-2023-34459 [MEDIUM] OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
### Impact
When the `verifyMultiProof`, `verifyMultiProofCalldata`, `processMultiProof`, or `processMultiProofCalldata` 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 inadvertently 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`
GHSA
OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
ghsa·2023-06-19
CVE-2023-34459 [MEDIUM] CWE-354 OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
OpenZeppelin Contracts using MerkleProof multiproofs may allow proving arbitrary leaves for specific trees
### Impact
When the `verifyMultiProof`, `verifyMultiProofCalldata`, `processMultiProof`, or `processMultiProofCalldata` 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 inadvertently 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`
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/OpenZeppelin/openzeppelin-contracts/commit/4d2383e17186be3e8ccf5a442e9686ecc7de1c55https://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.9.2https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wprv-93r4-jj2phttps://github.com/OpenZeppelin/openzeppelin-contracts/commit/4d2383e17186be3e8ccf5a442e9686ecc7de1c55https://github.com/OpenZeppelin/openzeppelin-contracts/releases/tag/v4.9.2https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories/GHSA-wprv-93r4-jj2p
2023-06-16
Published