ID CVE-2020-12825
Summary libcroco through 0.6.13 has excessive recursion in cr_parser_parse_any_core in cr-parser.c, leading to stack consumption.
References
Vulnerable Configurations
  • cpe:2.3:a:gnome:libcroco:0.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.8:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.8:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.9:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.9:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.10:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.10:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.11:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.11:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.12:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.12:*:*:*:*:*:*:*
  • cpe:2.3:a:gnome:libcroco:0.6.13:*:*:*:*:*:*:*
    cpe:2.3:a:gnome:libcroco:0.6.13:*:*:*:*:*:*:*
CVSS
Base: 5.8 (as of 08-09-2020 - 18:15)
Impact:
Exploitability:
CWE CWE-674
CAPEC
  • XML Oversized Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By supplying oversized payloads in input vectors that will be processed by the XML parser, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization, and potentially cause execution of arbitrary code. An adversary's goal is to leverage parser failure to his or her advantage. In many cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it is possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.231.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
  • XML Nested Payloads
    Applications often need to transform data in and out of the XML format by using an XML parser. It may be possible for an adversary to inject data that may have an adverse effect on the XML parser when it is being processed. By nesting XML data and causing this data to be continuously self-referential, an adversary can cause the XML parser to consume more resources while processing, causing excessive memory consumption and CPU utilization. An adversary's goal is to leverage parser failure to his or her advantage. In most cases this type of an attack will result in a XML Denial of Service (XDoS) due to an application becoming unstable, freezing, or crashing. However it may be possible to cause a crash resulting in arbitrary code execution, leading to a jump from the data plane to the control plane [R.230.1]. XDoS is most closely associated with web services, SOAP, and Rest, because remote service requesters can post malicious XML payloads to the service provider designed to exhaust the service provider's memory, CPU, and/or disk space. The main weakness in XDoS is that the service provider generally must inspect, parse, and validate the XML messages to determine routing, workflow, security considerations, and so on. It is exactly these inspection, parsing, and validation routines that XDoS targets. This attack exploits the loosely coupled nature of web services, where the service provider has little to no control over the service requester and any messages the service requester sends.
Access
VectorComplexityAuthentication
NETWORK MEDIUM NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL PARTIAL
cvss-vector via4 AV:N/AC:M/Au:N/C:N/I:P/A:P
redhat via4
advisories
bugzilla
id 1835377
title CVE-2020-12825 libcroco: Stack overflow in function cr_parser_parse_any_core in cr-parser.c
oval
OR
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 8 is installed
      oval oval:com.redhat.rhba:tst:20193384074
    • OR
      • AND
        • comment libcroco is earlier than 0:0.6.12-4.el8_2.1
          oval oval:com.redhat.rhsa:tst:20203654001
        • comment libcroco is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20183140330
      • AND
        • comment libcroco-debugsource is earlier than 0:0.6.12-4.el8_2.1
          oval oval:com.redhat.rhsa:tst:20203654003
        • comment libcroco-debugsource is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20203654004
      • AND
        • comment libcroco-devel is earlier than 0:0.6.12-4.el8_2.1
          oval oval:com.redhat.rhsa:tst:20203654005
        • comment libcroco-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20183140332
rhsa
id RHSA-2020:3654
released 2020-09-08
severity Moderate
title RHSA-2020:3654: libcroco security update (Moderate)
rpms
  • libcroco-0:0.6.12-4.el8_2.1
  • libcroco-debuginfo-0:0.6.12-4.el8_2.1
  • libcroco-debugsource-0:0.6.12-4.el8_2.1
  • libcroco-devel-0:0.6.12-4.el8_2.1
refmap via4
misc https://gitlab.gnome.org/GNOME/libcroco/-/issues/8
mlist
  • [oss-security] 20200813 Re: Re: [FD] libcroco multiple vulnerabilities
  • [oss-security] 20200908 Re: Re: [FD] libcroco multiple vulnerabilities
Last major update 08-09-2020 - 18:15
Published 12-05-2020 - 18:15
Last modified 08-09-2020 - 18:15
Back to Top