| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Asciidoctor 1.5.7.1. It has been declared as problematic. The affected element is an unknown function. Executing a manipulation can lead to resource management. This vulnerability is tracked as CVE-2018-18385. The attack can be launched remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in Asciidoctor 1.5.7.1. This vulnerability affects some unknown processing. The manipulation with an unknown input leads to a resource management vulnerability. The CWE definition for the vulnerability is CWE-399. As an impact it is known to affect availability. CVE summarizes:
Asciidoctor v1.5.7.1 allows remote attackers to cause a denial of service (infinite loop), as demonstrated by web applications that deliver untrusted input to this product, because Parser#next_block misuses a "while true" statement.
The bug was discovered 09/26/2018. The weakness was disclosed 10/16/2018 (Website). The advisory is available at github.com. This vulnerability was named CVE-2018-18385 since 10/16/2018. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available.
The vulnerability was handled as a non-public zero-day exploit for at least 20 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.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Resource managementCWE: CWE-399 / CWE-404
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
09/26/2018 🔍10/16/2018 🔍
10/16/2018 🔍
10/16/2018 🔍
10/17/2018 🔍
05/25/2023 🔍
Sources
Product: github.comAdvisory: 2888
Status: Not defined
CVE: CVE-2018-18385 (🔍)
GCVE (CVE): GCVE-0-2018-18385
GCVE (VulDB): GCVE-100-125362
Entry
Created: 10/17/2018 06:43Updated: 05/25/2023 15:01
Changes: 10/17/2018 06:43 (54), 04/02/2020 16:31 (1), 05/25/2023 15:01 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.