CVE-2020-12825
published 2020-05-12CVE-2020-12825: libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
PriorityP432high7.1CVSS 3.1
AVNACLPRNUIRSUCNILAH
EPSS
2.32%
81.3th percentile
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| gnome | libcroco | <= 0.6.13 | — |
| gnome | libcroco | >= 0 < 0.6.13-1ubuntu0.1 | 0.6.13-1ubuntu0.1 |
| gnome | libcroco | >= 0 < 0.6.8-2ubuntu1+esm1 | 0.6.8-2ubuntu1+esm1 |
| gnome | libcroco | >= 0 < 0.6.11-1ubuntu0.1~esm1 | 0.6.11-1ubuntu0.1~esm1 |
| gnome | libcroco | >= 0 < 0.6.12-2ubuntu0.1~esm1 | 0.6.12-2ubuntu0.1~esm1 |
| msrc | cbl2_libcroco_0.6.13-6_on_cbl_mariner_2.0 | — | — |
CVSS provenance
nvdv3.17.1HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H
nvdv2.05.8MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:P
osv7.1HIGH
vendor_msrc7.1HIGH
vendor_redhat7.1HIGH
vendor_ubuntu5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
Libcroco vulnerabilities
vendor_ubuntu·2024-08-13·CVSS 5.5
CVE-2017-8834 [MEDIUM] Libcroco vulnerabilities
Title: Libcroco vulnerabilities
Summary: Several security issues were fixed in Libcroco.
It was discovered that Libcroco was incorrectly accessing data structures
when reading bytes from memory, which could cause a heap buffer overflow.
An attacker could possibly use this issue to cause a denial of service.
This issue only affected Ubuntu 14.04 LTS. (CVE-2017-7960)
It was discovered that Libcroco was incorrectly handling invalid UTF-8
values when processing CSS files. An attacker could possibly use this
issue to cause a denial of service. (CVE-2017-8834, CVE-2017-8871)
It was discovered that Libcroco was incorrectly implementing recursion in
one of its parsing functions, which could cause an infinite recursion
loop and a stack overflow due to stack consumption. An attacker could
possib
Ubuntu
Libcroco vulnerabilities
vendor_ubuntu·2022-04-26·CVSS 5.5
CVE-2020-12825 [MEDIUM] Libcroco vulnerabilities
Title: Libcroco vulnerabilities
Summary: Several security issues were fixed in Libcroco.
It was discovered that Libcroco was incorrectly accessing data structures when
reading bytes from memory, which could cause a heap buffer overflow. An attacker
could possibly use this issue to cause a denial of service. (CVE-2017-7960)
It was discovered that Libcroco was incorrectly handling invalid UTF-8 values
when processing CSS files. An attacker could possibly use this issue to cause
a denial of service. (CVE-2017-8834, CVE-2017-8871)
It was discovered that Libcroco was incorrectly implementing recursion in one
of its parsing functions, which could cause an infinite recursion loop and a
stack overflow due to stack consumption. An attacker could possibly use this
issue to cause a denial of serv
Red Hat
libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
vendor_redhat·2020-05-12·CVSS 7.1
CVE-2020-12825 [HIGH] CWE-674 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
A stack overflow flaw was found in libcroco. A service using libcroco's CSS parser could be crashed by a local, authenticated attacker, or an attacker utilizing social engineering, using a crafted input. The highest threat from this vulnerability is to system availability.
Statement: While Red Hat Enterprise Linux 6, 7 and 8 ship versions of `libcroco` that are vulnerable to this flaw, the packages which use this library as a dependency would require a user to open a malicious file locally for exploitation. Opening such a file may result in a temporary crash of the application. See below for
Microsoft
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
vendor_msrc·2020-05-12·CVSS 7.1
CVE-2020-12825 [HIGH] CWE-674 libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information. If impact to additional products is identified, we will update the CVE to reflect this.
Mariner: Mariner
mitre: mitre
Customer Action Required
OSV
libcroco vulnerabilities
osv·2024-08-13·CVSS 5.5
CVE-2017-7960 [MEDIUM] libcroco vulnerabilities
libcroco vulnerabilities
It was discovered that Libcroco was incorrectly accessing data structures
when reading bytes from memory, which could cause a heap buffer overflow.
An attacker could possibly use this issue to cause a denial of service.
This issue only affected Ubuntu 14.04 LTS. (CVE-2017-7960)
It was discovered that Libcroco was incorrectly handling invalid UTF-8
values when processing CSS files. An attacker could possibly use this
issue to cause a denial of service. (CVE-2017-8834, CVE-2017-8871)
It was discovered that Libcroco was incorrectly implementing recursion in
one of its parsing functions, which could cause an infinite recursion
loop and a stack overflow due to stack consumption. An attacker could
possibly use this issue to cause a denial of service. (CVE-2020-12825)
GHSA
GHSA-23x2-xqxm-pxwj: libcroco through 0
ghsa_unreviewed·2022-05-24
CVE-2020-12825 [MEDIUM] CWE-674 GHSA-23x2-xqxm-pxwj: libcroco through 0
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
OSV
libcroco vulnerabilities
osv·2022-04-26·CVSS 5.5
CVE-2017-7960 [MEDIUM] libcroco vulnerabilities
libcroco vulnerabilities
It was discovered that Libcroco was incorrectly accessing data structures when
reading bytes from memory, which could cause a heap buffer overflow. An attacker
could possibly use this issue to cause a denial of service. (CVE-2017-7960)
It was discovered that Libcroco was incorrectly handling invalid UTF-8 values
when processing CSS files. An attacker could possibly use this issue to cause
a denial of service. (CVE-2017-8834, CVE-2017-8871)
It was discovered that Libcroco was incorrectly implementing recursion in one
of its parsing functions, which could cause an infinite recursion loop and a
stack overflow due to stack consumption. An attacker could possibly use this
issue to cause a denial of service. (CVE-2020-12825)
OSV
CVE-2020-12825: libcroco through 0
osv·2020-05-12·CVSS 7.1
CVE-2020-12825 [HIGH] CVE-2020-12825: libcroco through 0
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
bugzilla·2020-05-13·CVSS 7.1
CVE-2020-12825 [HIGH] CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this issue affects
Bugzilla
CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
bugzilla·2020-05-13·CVSS 7.1
CVE-2020-12825 [HIGH] CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
Upstream issue:
https://gitlab.gnome.org/GNOME/libcroco/-/issues/8
Discussion:
Created libcroco tracking bugs for this issue:
Affects: fedora-all [bug 1835378]
Created mingw-libcroco tracking bugs for this issue:
Affects: fedora-all [bug 1835379]
---
libcroco has a CSS2 parser which uses the function cr_parser_parse_any_core() in cr-parser.c to parse CSS "any" grammar. The function calls itself recursively when the tokenizer provides it with a token which is one of type: PO_TK (Opening parenthesis), BO_TK (Opening bracket), or FUNCTION_TK. It does not limit the recursi
Bugzilla
CVE-2020-12825 mingw-libcroco: libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
bugzilla·2020-05-13·CVSS 7.1
CVE-2020-12825 [HIGH] CVE-2020-12825 mingw-libcroco: libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
CVE-2020-12825 mingw-libcroco: libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: thi
http://www.openwall.com/lists/oss-security/2020/08/13/3http://www.openwall.com/lists/oss-security/2020/09/08/3https://gitlab.gnome.org/GNOME/libcroco/-/issues/8https://security.gentoo.org/glsa/202208-33http://www.openwall.com/lists/oss-security/2020/08/13/3http://www.openwall.com/lists/oss-security/2020/09/08/3https://gitlab.gnome.org/GNOME/libcroco/-/issues/8https://security.gentoo.org/glsa/202208-33
2020-05-12
Published