LibSass up to 3.5.4 Parser eval.cpp Binary_Expression*) resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability labeled as problematic has been found in LibSass up to 3.5.4. This impacts the function Sass::Eval::operator(Sass::Binary_Expression*) of the file eval.cpp of the component Parser. Such manipulation leads to resource consumption.
This vulnerability is documented as CVE-2018-19837. The attack can be executed remotely. There is not any exploit available.
The affected component should be upgraded.
Details
A vulnerability was found in LibSass up to 3.5.4 (Programming Language Software). It has been rated as problematic. Affected by this issue is the function Sass::Eval::operator(Sass::Binary_Expression*) of the file eval.cpp of the component Parser. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. CVE summarizes:
In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp.
The bug was discovered 06/02/2018. The weakness was released 12/04/2018 (Website). The advisory is available at github.com. This vulnerability is handled as CVE-2018-19837 since 12/03/2018. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1499 by the MITRE ATT&CK project.
The vulnerability was handled as a non-public zero-day exploit for at least 185 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 3.5.5 eliminates this vulnerability.
Entries connected to this vulnerability are available at VDB-127468 and VDB-127467. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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 consumptionCWE: CWE-400 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: LibSass 3.5.5
Patch: github.com
Timeline
06/02/2018 🔍12/03/2018 🔍
12/04/2018 🔍
12/04/2018 🔍
12/05/2018 🔍
06/12/2023 🔍
Sources
Advisory: 210fdff7a65370c2ae24e022a2b35da8c423cc5fStatus: Not defined
CVE: CVE-2018-19837 (🔍)
GCVE (CVE): GCVE-0-2018-19837
GCVE (VulDB): GCVE-100-127466
See also: 🔍
Entry
Created: 12/05/2018 08:14Updated: 06/12/2023 16:27
Changes: 12/05/2018 08:14 (61), 04/17/2020 11:05 (1), 06/12/2023 16:27 (5)
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.