OpenZeppelin openzeppelin-contracts 4.9.4 Subcall control flow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in OpenZeppelin openzeppelin-contracts 4.9.4. This affects an unknown part of the component Subcall Handler. The manipulation leads to control flow. This vulnerability is uniquely identified as CVE-2023-49798. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in OpenZeppelin openzeppelin-contracts 4.9.4. It has been rated as problematic. This issue affects some unknown processing of the component Subcall Handler. The manipulation with an unknown input leads to a control flow vulnerability. Using CWE to declare the problem leads to CWE-670. The code contains a control flow path that does not reflect the algorithm that the path is intended to implement, leading to incorrect behavior any time this path is navigated. Impacted is integrity. The summary by CVE is:
OpenZeppelin Contracts is a library for smart contract development. A merge issue when porting the 5.0.1 patch to the 4.9 branch caused a line duplication. In the version of `Multicall.sol` released in `@openzeppelin/[email protected]` and `@openzeppelin/[email protected]`, all subcalls are executed twice. Concretely, this exposes a user to unintentionally duplicate operations like asset transfers. The duplicated delegatecall was removed in version 4.9.5. The 4.9.4 version is marked as deprecated. Users are advised to upgrade. There are no known workarounds for this issue.
The weakness was disclosed 12/09/2023 as GHSA-699g-q6qh-q4v8. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-49798 since 11/30/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.9.5 eliminates this vulnerability. Applying the patch 88ac712e06832bce73b41e8166cded2729e25205 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.9
CNA Vector (GitHub, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Control flowCWE: CWE-670
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: openzeppelin-contracts 4.9.5
Patch: 88ac712e06832bce73b41e8166cded2729e25205
Timeline
11/30/2023 🔍12/09/2023 🔍
12/09/2023 🔍
01/01/2024 🔍
Sources
Product: github.comAdvisory: GHSA-699g-q6qh-q4v8
Status: Confirmed
CVE: CVE-2023-49798 (🔍)
GCVE (CVE): GCVE-0-2023-49798
GCVE (VulDB): GCVE-100-247337
Entry
Created: 12/09/2023 09:15Updated: 01/01/2024 08:25
Changes: 12/09/2023 09:15 (52), 01/01/2024 08:25 (11)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.