CVE-2017-7961

Exp

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.

Published: 2017-04-19 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-7961 is rated High Exploit Risk (74.5/100): CVSS High severity, with medium exploitation likelihood (EPSS 1.97%). 1 public exploit reference(s) are indexed (Exploit-DB). EPSS rose +1.10% over the last day, indicating growing attacker interest. Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2017-7961

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2017-7961

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.87% 1.97% +1.10%
2 2025-11-21 0.62% 0.87% +0.25%
3 2025-11-18 — 0.62% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-7961

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
7.8 3.0 HIGH
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.9 [email protected]
6.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 8.6 6.4 [email protected]

Weakness enumeration for CVE-2017-7961

OS Trackers for CVE-2017-7961

vendor priority summary link
alpine — CVE-2017-7961: 1 source package rows (libcroco); 2 state rows across 2 repos (3.10-main, 3.11-main); fixed 2, open 0. https://security.alpinelinux.org/vuln/CVE-2017-7961
gentoo normal CVE-2017-7961: 1 GLSA(s) (201707-13), 1 atom(s) (dev-libs/libcroco); latest impact normal. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2017-7961
redhat low — https://access.redhat.com/security/cve/CVE-2017-7961
suse low CVE-2017-7961 severity low: SUSE including 33 source package names (libcroco, libcroco-0.6.11-12.3.1, …), 122 product×package rows across 60 product lines (Image SLES12-SP5-Azure-BYOS, Image SLES12-SP5-Azure-Basic-On-Demand, … (60 product lines)): Fixed 89, Known Not Affected 33. https://www.suse.com/security/cve/CVE-2017-7961/
ubuntu low CVE-2017-7961 low priority: Ubuntu including 1 source packages (libcroco), 12 status rows across 12 suites (artful, bionic, cosmic, disco, eoan, focal, precise, trusty, upstream, xenial, yakkety, zesty): ignored 6, not-affected 5, released 1. https://ubuntu.com/security/CVE-2017-7961

Affected software / configurations for CVE-2017-7961

Vendor Product Version Raw CPE
gnome libcroco 0.6.11 cpe:2.3:a:gnome:libcroco:0.6.11:*:*:*:*:*:*:*
gnome libcroco 0.6.12 cpe:2.3:a:gnome:libcroco:0.6.12:*:*:*:*:*:*:*

References for CVE-2017-7961

cvelogic Threat Intelligence