libxml2 through 2.11.5 has a use-after-free that can only occur after a certain memory allocation fails. This occurs in xmlUnlinkNode in tree.c. NOTE: the vendor's position is "I don't think these issues are critical enough to warrant a CVE ID ... because an attacker typically can't control when memory allocations fail."
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://gitlab.gnome.org/GNOME/libxml2/-/issues/583 | patch vendor advisory issue tracking |
https://gitlab.gnome.org/GNOME/libxml2/-/issues/344 | patch vendor advisory issue tracking |
http://www.openwall.com/lists/oss-security/2023/10/06/5 | patch mailing list third party advisory |