In libexpat in Expat before 2.2.7, XML input including XML names that contain a large number of colons could make the XML parser consume a high amount of RAM and CPU resources while processing (enough to be usable for denial-of-service attacks). External References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931031 Upstream Issue: https://github.com/libexpat/libexpat/issues/186
Created expat tracking bugs for this issue: Affects: fedora-all [bug 1723724] Created mingw-expat tracking bugs for this issue: Affects: epel-7 [bug 1723726] Affects: fedora-all [bug 1723725]
This vulnerability is out of security support scope for the following products: * Red Hat Enterprise Application Platform 6 * Red Hat JBoss Enterprise Web Server 2 Please refer to https://access.redhat.com/support/policy/updates/jboss_notes for more details.
Patch: https://github.com/libexpat/libexpat/commit/11f8838bf99ea0a6f0b76f9760c43704d00c4ff6
Statement: When processing a specially crafted XML file, expat may use more memory than ultimately necessary, which can also lead to increased CPU usage and longer processing times. Depending on available system resources and configuration, this may also lead to the application triggering the Out-Of-Memory-Killer, causing the application to be terminated.
Is there any plan to provide a patch for expat in RHEL7 and RHEL8 for this moderate severity issue? If so is there an ETA for those patches?
This issue has been addressed in the following products: JBoss Core Services on RHEL 6 JBoss Core Services on RHEL 7 Via RHSA-2020:2644 https://access.redhat.com/errata/RHSA-2020:2644
This issue has been addressed in the following products: Red Hat JBoss Core Services Via RHSA-2020:2646 https://access.redhat.com/errata/RHSA-2020:2646
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2018-20843
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2020:3952 https://access.redhat.com/errata/RHSA-2020:3952
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4484 https://access.redhat.com/errata/RHSA-2020:4484
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:4846 https://access.redhat.com/errata/RHSA-2020:4846