An issue was discovered in libxml2 before 2.10.3. Certain invalid XML entity definitions can corrupt a hash table key, potentially leading to subsequent logic errors. In one case, a double-free can be provoked.
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libxml2 | Xmlsoft | * | 2.10.3 (excluding) |
| Red Hat Enterprise Linux 8 | RedHat | libxml2-0:2.9.7-15.el8_7.1 | * |
| Red Hat Enterprise Linux 8 | RedHat | libxml2-0:2.9.7-15.el8_7.1 | * |
| Red Hat Enterprise Linux 8.6 Extended Update Support | RedHat | libxml2-0:2.9.7-13.el8_6.4 | * |
| Red Hat Enterprise Linux 9 | RedHat | libxml2-0:2.9.13-3.el9_1 | * |
| Red Hat Enterprise Linux 9 | RedHat | libxml2-0:2.9.13-3.el9_1 | * |
| Red Hat JBoss Core Services 1 | RedHat | libxml2 | * |
| Libxml2 | Ubuntu | bionic | * |
| Libxml2 | Ubuntu | esm-infra/xenial | * |
| Libxml2 | Ubuntu | focal | * |
| Libxml2 | Ubuntu | jammy | * |
| Libxml2 | Ubuntu | kinetic | * |
| Libxml2 | Ubuntu | trusty | * |
| Libxml2 | Ubuntu | trusty/esm | * |
| Libxml2 | Ubuntu | upstream | * |
| Libxml2 | Ubuntu | xenial | * |