WebKit JavaScriptCore runtime/JSONObject.cpp JSONstringify input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WebKit and classified as problematic. Impacted is the function JSONstringify of the file runtime/JSONObject.cpp of the component JavaScriptCore. Such manipulation leads to input validation.
This vulnerability is documented as CVE-2016-10222. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability, which was classified as problematic, has been found in WebKit (Web Browser) (the affected version is unknown). Affected by this issue is the function JSONstringify of the file runtime/JSONObject.cpp of the component JavaScriptCore. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. CVE summarizes:
runtime/JSONObject.cpp in JavaScriptCore in WebKit, as distributed in Safari Technology Preview Release 18, allows remote attackers to cause a denial of service (segmentation violation and application crash) via crafted JavaScript code that triggers a "type confusion" in the JSON.stringify function.
The bug was discovered 10/28/2016. The weakness was released 04/03/2017 (Website). The advisory is shared for download at trac.webkit.org. This vulnerability is handled as CVE-2016-10222 since 02/09/2017. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 157 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.
Entry connected to this vulnerability is available at VDB-99237. Once again VulDB remains the best source for vulnerability data.
Product
Type
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
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: 🔍
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/28/2016 🔍02/09/2017 🔍
04/03/2017 🔍
04/03/2017 🔍
04/03/2017 🔍
11/24/2022 🔍
Sources
Advisory: 208123Status: Not defined
Confirmation: 🔍
CVE: CVE-2016-10222 (🔍)
GCVE (CVE): GCVE-0-2016-10222
GCVE (VulDB): GCVE-100-99236
OSVDB: - CVE-2016-10222 - WebKit - Denial of Service Issue
See also: 🔍
Entry
Created: 04/03/2017 16:55Updated: 11/24/2022 17:26
Changes: 04/03/2017 16:55 (58), 08/25/2020 11:20 (3), 11/24/2022 17:26 (3)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.