libcroco 0.6.11/0.6.12 CSS File cr-tknzr.c cr_tknzr_parse_rgb memory corruption ⚔ [Disputed]

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.5$0-$5k0.00

Summaryinfo

A vulnerability was found in libcroco 0.6.11/0.6.12. It has been declared as critical. The affected element is the function cr_tknzr_parse_rgb of the file cr-tknzr.c of the component CSS File Handler. The manipulation results in memory corruption. This vulnerability is known as CVE-2017-7961. It is possible to launch the attack remotely. No exploit is available. The real existence of this vulnerability is still doubted at the moment. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in libcroco 0.6.11/0.6.12. Affected is the function cr_tknzr_parse_rgb of the file cr-tknzr.c of the component CSS File Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

The cr_tknzr_parse_rgb function in cr-tknzr.c in libcroco 0.6.11 and 0.6.12 has an "outside the range of representable values of type long" undefined behavior issue, which might allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via a crafted CSS file. NOTE: third-party analysis reports "This is not a security issue in my view. The conversion surely is truncating the double into a long value, but there is no impact as the value is one of the RGB components.

The bug was discovered 04/12/2017. The weakness was published 04/19/2017 (Website). The advisory is shared for download at openwall.com. This vulnerability is traded as CVE-2017-7961 since 04/19/2017. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $0-$5k. The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 99603 (Debian DLA-909-1 : libcroco security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. 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)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 4 days after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (99603). Similar entries are available at VDB-100259, VDB-102231 and VDB-102232. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.6
VulDB Meta Temp Score: 7.5

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.8
NVD Vector: 🔍

CNA Base Score: 7.8
CNA Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 99603
Nessus Name: Debian DLA-909-1 : libcroco security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 865445
OpenVAS Name: Debian LTS Advisory ([SECURITY] [DLA 909-1] libcroco security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Patch: git.gnome.org

Timelineinfo

04/12/2017 🔍
04/19/2017 +7 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/19/2017 +0 days 🔍
04/23/2017 +4 days 🔍
04/24/2017 +1 days 🔍
07/03/2024 +2627 days 🔍

Sourcesinfo

Advisory: openwall.com
Status: Confirmed
Disputed: 🔍

CVE: CVE-2017-7961 (🔍)
GCVE (CVE): GCVE-0-2017-7961
GCVE (VulDB): GCVE-100-100260
OSVDB: - CVE-2017-7961 - libcroco - Denial of Service Issue

See also: 🔍

Entryinfo

Created: 04/19/2017 22:12
Updated: 07/03/2024 13:42
Changes: 04/19/2017 22:12 (74), 09/17/2020 18:28 (4), 12/01/2022 13:42 (4), 06/04/2024 21:38 (27), 07/03/2024 13:42 (2)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!