In xsltCopyText in transform.c in libxslt 1.1.33, a pointer variable isnt reset under certain circumstances. If the relevant memory area happened to be freed and reused in a certain way, a bounds check could fail and memory outside a buffer could be written to, or uninitialized data could be disclosed.
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.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Libxslt | Xmlsoft | 1.1.33 (including) | 1.1.33 (including) |
| Red Hat Enterprise Linux 6 Supplementary | RedHat | chromium-browser-0:80.0.3987.87-1.el6_10 | * |
| Red Hat Enterprise Linux 7 | RedHat | libxslt-0:1.1.28-6.el7 | * |
| Red Hat Enterprise Linux 8 | RedHat | libxslt-0:1.1.32-5.el8 | * |
| Red Hat Enterprise Linux 8 | RedHat | libxslt-0:1.1.32-5.el8 | * |
| Libxslt | Ubuntu | bionic | * |
| Libxslt | Ubuntu | disco | * |
| Libxslt | Ubuntu | eoan | * |
| Libxslt | Ubuntu | esm-infra-legacy/trusty | * |
| Libxslt | Ubuntu | esm-infra/bionic | * |
| Libxslt | Ubuntu | esm-infra/xenial | * |
| Libxslt | Ubuntu | trusty | * |
| Libxslt | Ubuntu | trusty/esm | * |
| Libxslt | Ubuntu | xenial | * |