Ethereum Solidity 0.8.14 SMTEncoder.cpp indexOrMemberAssignment assertion
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Ethereum Solidity 0.8.14 and classified as problematic. This vulnerability affects the function SMTEncoder::indexOrMemberAssignment
of the file SMTEncoder.cpp. The manipulation leads to assertion.
This vulnerability was named CVE-2022-33069. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability, which was classified as problematic, was found in Ethereum Solidity 0.8.14. This affects the function SMTEncoder::indexOrMemberAssignment
of the file SMTEncoder.cpp. The manipulation with an unknown input leads to a assertion vulnerability. CWE is classifying the issue as CWE-617. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. This is going to have an impact on availability. The summary by CVE is:
Ethereum Solidity v0.8.14 contains an assertion failure via SMTEncoder::indexOrMemberAssignment() at SMTEncoder.cpp.
The weakness was disclosed 06/24/2022 as 12973. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2022-33069 since 06/13/2022. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: AssertionCWE: CWE-617
CAPEC: 🔍
ATT&CK: 🔍
Local: No
Remote: Partially
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/13/2022 🔍06/24/2022 🔍
06/24/2022 🔍
06/24/2022 🔍
Sources
Advisory: 12973Status: Confirmed
CVE: CVE-2022-33069 (🔍)
GCVE (CVE): GCVE-0-2022-33069
GCVE (VulDB): GCVE-100-202557
Entry
Created: 06/24/2022 06:48 AMChanges: 06/24/2022 06:48 AM (39)
Complete: 🔍
Cache ID: 18:90C:40
No comments yet. Languages: en.
Please log in to comment.