CVE-2023-52425
Libexpat denial of service
- Published4 Feb 2024
Description
libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://github.com/libexpat/libexpat/pull/789
- https://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://lists.fedoraproject.org/archives/list/[email protected]/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://security.netapp.com/advisory/ntap-20240614-0003/
- http://www.openwall.com/lists/oss-security/2024/03/20/5
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2023-52425 being actively exploited?
CVE-2023-52425 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 1.81%.
How severe is CVE-2023-52425?
CVE-2023-52425 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 1.81% probability of exploitation.
Which products are affected by CVE-2023-52425?
Affected products include Libexpat.
How do I fix CVE-2023-52425?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2023-52425 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.