WAVM up to 2018-07-26 WebAssembly Virtual Machine Errors::unreachable input validation
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in WAVM up to 2018-07-26. This vulnerability affects the function Errors::unreachable
of the component WebAssembly Virtual Machine. The manipulation leads to input validation.
This vulnerability was named CVE-2018-16766. The attack can be initiated remotely. There is no exploit available.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability classified as problematic has been found in WAVM up to 2018-07-26. This affects the function Errors::unreachable
of the component WebAssembly Virtual Machine. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. This is going to have an impact on availability. The summary by CVE is:
In WAVM through 2018-07-26, a crafted file sent to the WebAssembly Virtual Machine may cause a denial of service (application crash) or possibly have unspecified other impact because Errors::unreachable() is reached.
The bug was discovered 07/26/2018. The weakness was disclosed 09/10/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-16766 since 09/09/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 46 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-123781, VDB-123780, VDB-123779 and VDB-123778 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.5
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
07/26/2018 🔍09/09/2018 🔍
09/10/2018 🔍
09/10/2018 🔍
09/10/2018 🔍
05/07/2023 🔍
Sources
Advisory: 96Status: Not defined
CVE: CVE-2018-16766 (🔍)
GCVE (CVE): GCVE-0-2018-16766
GCVE (VulDB): GCVE-100-123777
See also: 🔍
Entry
Created: 09/10/2018 07:34 AMUpdated: 05/07/2023 04:36 PM
Changes: 09/10/2018 07:34 AM (57), 03/22/2020 08:13 AM (1), 05/07/2023 04:36 PM (3)
Complete: 🔍
Cache ID: 18:842:40
No comments yet. Languages: en.
Please log in to comment.