rpm package
opensuse/python-libxml2-python&distro=openSUSE Leap 15.4
pkg:rpm/opensuse/python-libxml2-python&distro=openSUSE%20Leap%2015.4
Vulnerabilities (10)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2023-45322 | — | < 2.9.7-150000.3.63.1 | 2.9.7-150000.3.63.1 | Oct 6, 2023 | 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 ca | ||
| CVE-2023-39615 | — | < 2.9.7-150000.3.60.1 | 2.9.7-150000.3.60.1 | Aug 29, 2023 | Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the prod | ||
| CVE-2023-29469 | — | < 2.9.7-150000.3.57.1 | 2.9.7-150000.3.57.1 | Apr 24, 2023 | An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there | ||
| CVE-2023-28484 | — | < 2.9.7-150000.3.57.1 | 2.9.7-150000.3.57.1 | Apr 24, 2023 | In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c. | ||
| CVE-2022-40304 | — | < 2.9.7-150000.3.51.1 | 2.9.7-150000.3.51.1 | Nov 23, 2022 | 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. | ||
| CVE-2022-40303 | — | < 2.9.7-150000.3.51.1 | 2.9.7-150000.3.51.1 | Nov 22, 2022 | An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmen | ||
| CVE-2016-3709 | — | < 2.9.7-150000.3.51.1 | 2.9.7-150000.3.51.1 | Jul 28, 2022 | Possible cross-site scripting vulnerability in libxml after commit 960f0e2. | ||
| CVE-2022-29824 | — | < 2.9.7-150000.3.46.1 | 2.9.7-150000.3.46.1 | May 3, 2022 | In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software usin | ||
| CVE-2022-23308 | — | < 2.9.7-150000.3.46.1 | 2.9.7-150000.3.46.1 | Feb 26, 2022 | valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes. | ||
| CVE-2021-3541 | — | < 2.9.7-150000.3.57.1 | 2.9.7-150000.3.57.1 | Jul 9, 2021 | A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service. |
- CVE-2023-45322Oct 6, 2023affected < 2.9.7-150000.3.63.1fixed 2.9.7-150000.3.63.1
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 ca
- CVE-2023-39615Aug 29, 2023affected < 2.9.7-150000.3.60.1fixed 2.9.7-150000.3.60.1
Xmlsoft Libxml2 v2.11.0 was discovered to contain an out-of-bounds read via the xmlSAX2StartElement() function at /libxml2/SAX2.c. This vulnerability allows attackers to cause a Denial of Service (DoS) via supplying a crafted XML file. NOTE: the vendor's position is that the prod
- CVE-2023-29469Apr 24, 2023affected < 2.9.7-150000.3.57.1fixed 2.9.7-150000.3.57.1
An issue was discovered in libxml2 before 2.10.4. When hashing empty dict strings in a crafted XML document, xmlDictComputeFastKey in dict.c can produce non-deterministic values, leading to various logic and memory errors, such as a double free. This behavior occurs because there
- CVE-2023-28484Apr 24, 2023affected < 2.9.7-150000.3.57.1fixed 2.9.7-150000.3.57.1
In libxml2 before 2.10.4, parsing of certain invalid XSD schemas can lead to a NULL pointer dereference and subsequently a segfault. This occurs in xmlSchemaFixupComplexType in xmlschemas.c.
- CVE-2022-40304Nov 23, 2022affected < 2.9.7-150000.3.51.1fixed 2.9.7-150000.3.51.1
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.
- CVE-2022-40303Nov 22, 2022affected < 2.9.7-150000.3.51.1fixed 2.9.7-150000.3.51.1
An issue was discovered in libxml2 before 2.10.3. When parsing a multi-gigabyte XML document with the XML_PARSE_HUGE parser option enabled, several integer counters can overflow. This results in an attempt to access an array at a negative 2GB offset, typically leading to a segmen
- CVE-2016-3709Jul 28, 2022affected < 2.9.7-150000.3.51.1fixed 2.9.7-150000.3.51.1
Possible cross-site scripting vulnerability in libxml after commit 960f0e2.
- CVE-2022-29824May 3, 2022affected < 2.9.7-150000.3.46.1fixed 2.9.7-150000.3.46.1
In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software usin
- CVE-2022-23308Feb 26, 2022affected < 2.9.7-150000.3.46.1fixed 2.9.7-150000.3.46.1
valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.
- CVE-2021-3541Jul 9, 2021affected < 2.9.7-150000.3.57.1fixed 2.9.7-150000.3.57.1
A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.