libcroco 0.6.12 CSS File cr-parser.c cr_parser_parse_selector_core resource management

Summaryinfo

A vulnerability was found in libcroco 0.6.12 and classified as problematic. This impacts the function cr_parser_parse_selector_core of the file cr-parser.c of the component CSS File Handler. Executing a manipulation can lead to resource management. This vulnerability is tracked as CVE-2017-8871. The attack can be launched remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability classified as problematic was found in libcroco 0.6.12. This vulnerability affects the function cr_parser_parse_selector_core of the file cr-parser.c of the component CSS File Handler. 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:

The cr_parser_parse_selector_core function in cr-parser.c in libcroco 0.6.12 allows remote attackers to cause a denial of service (infinite loop and CPU consumption) via a crafted CSS file.

The bug was discovered 06/07/2017. The weakness was disclosed 06/12/2017 by qflb.wu as EDB-ID 42147 as not defined exploit (Exploit-DB). The advisory is shared for download at exploit-db.com. This vulnerability was named CVE-2017-8871 since 05/09/2017. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known.

A public exploit has been developed by qflb.wu and been published even before and not after the advisory. It is possible to download the exploit at github.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 5 days. During that time the estimated underground price was around $0-$5k. The commercial vulnerability scanner Qualys is able to test this issue with plugin 172445 (SUSE Enterprise Linux Security Update for libcroco (SUSE-SU-2019:1468-1)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Exploit-DB (42147). The entries VDB-100259, VDB-100260 and VDB-102231 are pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• libcroco

Version

• 0.6.12

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion