OpenZeppelin Contracts up to 0.6.0 signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in OpenZeppelin Contracts up to 0.6.0. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in signature verification. This vulnerability is reported as CVE-2023-23940. No exploit exists. It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in OpenZeppelin Contracts up to 0.6.0. This affects an unknown code. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was disclosed 02/03/2023. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-23940 since 01/19/2023. Neither technical details nor an exploit are publicly available.
Upgrading to version 0.6.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.3
NVD Vector: 🔍
CNA Base Score: 6.4
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: Signature verificationCWE: CWE-347 / CWE-345
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: Contracts 0.6.1
Patch: github.com
Timeline
01/19/2023 🔍02/03/2023 🔍
02/03/2023 🔍
03/04/2023 🔍
Sources
Advisory: GHSA-626q-v9j4-mcp4Status: Confirmed
CVE: CVE-2023-23940 (🔍)
GCVE (CVE): GCVE-0-2023-23940
GCVE (VulDB): GCVE-100-220077
Entry
Created: 02/03/2023 01:56Updated: 03/04/2023 10:23
Changes: 02/03/2023 01:56 (37), 03/04/2023 10:17 (3), 03/04/2023 10:23 (21)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.