CVE-2024-56171: Use After Free

Published Feb 18, 2025
·
Updated

Accessibility. A logging issue was addressed with improved data redaction.

Other sources

AccountPolicy. This issue was addressed by removing the vulnerable code.

— Apple

Accounts. This issue was addressed with improved data access restriction.

— Apple

AirDrop. A permissions issue was addressed with additional restrictions.

— Apple

AirPlay. A null pointer dereference was addressed with improved input validation.

— Apple

AirPlay. A type confusion issue was addressed with improved checks.

— Apple

Credit

Uri Katz (Oligo Security), Hossein Lotfi@@hosselot(Trend Micro Zero Day Initiative), Denis Tokarev@@illusionofcha0s, Google Threat Analysis Group, wac(Trend Micro Zero Day Initiative), pattern-f@@pattern_F_, Jonathan Bar Or@@yo_yo_yo_jbo(Microsoft), an anonymous researcher, CVE-2024-9681, LFY@@secsys(Fudan University), Anonymous(Trend Micro Zero Day Initiative), Michael (Biscuit) Thomas - @social.lol@@biscuit, Ian Beer(Google Project Zero), CVE-2024-48958, CVE-2025-27113, CVE-2024-56171, Alex Radocea(Supernetworks), Dave G.(Supernetworks), 风沐云烟@@binary_fmyy, Minghao Lin@@Y1nKoc, Jimmy, Mickey Jin@@patch1t, Bing Shi(Alibaba Group), Wenchao Li(Alibaba Group), Xiaolong Bai(Alibaba Group), Luyi Xing(Indiana University Bloomington), Halle Winkler, Politepix theoffcuts.org, Kirin@@Pwnrin, Bohdan Stasiuk@@bohdan_stasiuk, Gary Kwong, Paul Bakker(ParagonERP), Francisco Alonso@@revskills, rheza@@ginggilBesel, Ron Masas(BREAKPOINT), Dominik Rath, Martin Kreichgauer(Google Chrome), Yutong Xiu@@Sou1gh0st, Andr.Ess, Wang Yu(Cyberserval), @@RenwaX23, Syarif Muhammad Sajjad, Andrew James Gonzalez, Apple, CVE-2025-24085, Jax Reissner, Richard Hyunho Im with routezero.security@@richeeta, YingQi Shi@@Mas0nShi(DBAppSecurity's WeBin lab), Lukas Bernhard, Tashita Software Security, Xiangwei Zhang(Tencent Security YUNDING LAB), linjy(HKUS3Lab), chluo(WHUSecLab), Brendon Tiszka(Google Project Zero), Lehan Dilusha@@zafer, Zhongcheng Li(IES Red Team of ByteDance), Wojciech Regula(SecuRing), Claudio Bozzato(Cisco Talos), Francesco Benvenuto(Cisco Talos), Jeffrey Hofmann, Ian Mckay@@iann0036, Csaba Fitzl@@theevilbit(Kandji), Nolan Astrein(Kandji), Stephan Casas, Gergely Kalman@@gergely_kalman, Rodolphe BRUNETTI@@eisw0lf(Lupus Nova), Pietro Francesco Tirenna(Shielder), Davide Silvetti(Shielder), Abdel Adim Oisfi(Shielder), luckyu@@uuulucky, Rodolphe BRUNETTI@@eisw0lf, Manuel Fernandez (Stackhopper Security), ABC Research s.r.o., Murray Mike, mzzzz__, Dayton Pidhirney(Atredis Partners), Lyutoon, YenKoc, Ye Zhang@@VAR10CK(Baidu Security), Koh M. Nakagawa@@tsunek0h(FFRI Security Inc), Joseph Ravichandran@@0xjprx(MIT CSAIL), Kenneth Chew, Paweł Płatek (Trail(Bits), Alexia Wilson(Microsoft), Christine Fossaceca(Microsoft), Diamant Osmani & Valdrin Haliti [Kosovë], dbpeppe, Solitechworld, Pwn2car, Alhour@@NSAntoine, Mickey Jin@@patch1t(Kandji), (Kandji), Pedro Tôrres@@t0rr3sp3dr0, Noah Gregory (wts.dev), CVE-2023-27043, Jaydev Ahire, Yiğit Can YILMAZ@@yilmazcanyigit, Arsenii Kostromin (0x3c3e), Rodolphe Brunetti@@eisw0lf(Lupus Nova), Dolf Hoegaerts, Michiel Devliegere, K宝@@Pwnrin, Tong Liu@@Lyutoon_, 风(binary_fmyy), F00L, Dave G., zbleet(QI), Cristian Dinca(Computer Science), Romania, 风沐云烟 (binary_fmyy), Kirin, FlowerCode, Zhongquan Li@@Guluisacat, Pedro José Pereira Vieito / pvieito.com)@@pvieito, Alexander Heinrich@@Sn0wfreeze, SEEMOO, TU Darmstadt & Mathy Vanhoef@@vanhoefm, Jeroen Robben@@RobbenJeroen, DistriNet, KU Leuven, Vsevolod Kokorin (Slonser)(Solidlab), PixiePoint Security, Andreas Hegenberg (folivora.AI GmbH), Muhammad Zaid Ghifari (Mr.ZheeV), Kalimantan Utara, Florian Draschbacher, Dalibor Milanovic, Abhay Kailasia@@abhay_kailasia(C), Chi Yuan Chang(ZUSO ART), taikosoup, Murray Mike(Trend Micro Zero Day Initiative), 风沐云烟@@binary_fmyy(Supernetworks), Minghao Lin@@Y1nKoc(Supernetworks), Csaba Fitzl@@theevilbit(OffSec), 风沐云烟 (binary_fmyy)(DBAppSecurity's WeBin lab), Minghao Lin@@Y1nKoc(DBAppSecurity's WeBin lab), Junsung <3(Trend Micro Zero Day Initiative)

Affected Software

43 affected componentsFixes available
Gnome libxml2<2.12.10, >2.13.0<=2.13.6
F5 Traffix SDC=5.2.0
5.2.0
Xmlsoft Libxml2<2.12.10
Xmlsoft Libxml2>=2.13.0<2.13.6
All of the following
NetApp Hci Compute Node
NetApp Hci Compute Node
All of the following
NetApp H410c Firmware
NetApp H410c
All of the following
NetApp H300s Firmware
NetApp H300s
All of the following
NetApp H500s Firmware
NetApp H500s
All of the following
NetApp H700s Firmware
NetApp H700s
All of the following
NetApp H410s Firmware
NetApp H410s
NetApp Active Iq Unified Manager Vsphere
NetApp Manageability Software Development Kit
NetApp Ontap=9
NetApp Solidfire \& Hci Management Node
Apple tvOS<18.4
18.4
Apple WatchOS<11.4
11.4
Microsoft cbl2 libxml2 2.10.4-6
Patch available
Microsoft azl3 libxml2 2.11.5-5
Patch available
Microsoft azl3 libxml2 2.11.5-4
Patch available
Apple iPadOS<17.7.6
17.7.6
Apple macOS Sequoia<15.4
15.4
Apple iOS<18.4
18.4
Apple iPadOS<18.4
18.4
Apple macOS Sonoma<14.7.5
14.7.5
Apple visionOS<2.4
2.4
Apple macOS Ventura<13.7.5
13.7.5
alpine/libxml2>=2.13.0<2.11.8-r1
2.11.8-r1
alpine/libxml2>=2.13.0<2.11.8-r1
2.11.8-r1
alpine/libxml2>=2.13.0<2.12.7-r1
2.12.7-r1
alpine/libxml2>=2.13.0<2.13.4-r4
2.13.4-r4
alpine/libxml2>=2.13.0<2.13.6-r0
2.13.6-r0
alpine/libxml2>=2.13.0<2.13.6-r0
2.13.6-r0
alpine/libxml2>=2.13.0<2.13.6-r0
2.13.6-r0
debian/libxml2
2.9.14+dfsg-1.3~deb12u62.9.14+dfsg-1.3~deb12u42.12.7+dfsg+really2.9.14-2.1+deb13u32.12.7+dfsg+really2.9.14-2.1+deb13u12.15.4+dfsg-1
debian/libxml2<2.9.14+dfsg-1.3~deb12u2
2.9.14+dfsg-1.3~deb12u2
debian/libxml2<2.12.7+dfsg+really2.9.14-0.4
2.12.7+dfsg+really2.9.14-0.4
debian/libxml2<2.12.7+dfsg+really2.9.14-0.4
2.12.7+dfsg+really2.9.14-0.4

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/libxml2 to a version that resolves this vulnerability.

    Fixed in 2.9.10+dfsg-6.7+deb11u6
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 17.7.6
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 5.2.0
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.4
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 18.4
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 11.4
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 15.4
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 14.7.5
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 13.7.5
  10. Upgrade

    Upgrade libxml2 to a version that resolves this vulnerability.

    Fixed in 2.12.10
  11. Upgrade

    Upgrade libxml2 to a version that resolves this vulnerability.

    Fixed in 2.13.6
  12. Upgrade

    Upgrade libxml2 to a version that resolves this vulnerability.

    Fixed in 2.13.x

Event History

Feb 18, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·10:15 PM
DescriptionSeverityAffected Software
Data Sourced
via Red Hat·11:01 PM
DescriptionSeverityAffected Software
Feb 27, 2025
Data Sourced
via Microsoft·08:00 AM
DescriptionSeverityWeaknessAffected Software
Mar 31, 2025
Data Sourced
via Apple·12:00 AM
DescriptionWeaknessAffected Software
Aug 8, 2025
Advisory Published
via F5·08:15 PM
Data Sourced
via F5·08:15 PM
DescriptionSeverityWeaknessAffected Software
Jan 30, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-56171?

CVE-2024-56171 has a high severity due to the potential for exploitation through crafted XML documents.

2

How do I fix CVE-2024-56171?

To fix CVE-2024-56171, upgrade libxml2 to version 2.12.10 or 2.13.6 or later.

3

What versions of libxml2 are affected by CVE-2024-56171?

CVE-2024-56171 affects libxml2 versions before 2.12.10 and 2.13.0 through 2.13.5.

4

Can CVE-2024-56171 be exploited remotely?

Yes, CVE-2024-56171 can be exploited remotely if a vulnerable version processes untrusted XML documents.

5

What types of applications are at risk from CVE-2024-56171?

Applications that use affected versions of libxml2 for XML processing and validation are at risk from CVE-2024-56171.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203