rpm package
suse/python-libxml2-python&distro=SUSE Linux Enterprise Module for Python 2 15 SP3
pkg:rpm/suse/python-libxml2-python&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Python%202%2015%20SP3
Vulnerabilities (10)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| 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-3.37.1 | 2.9.7-3.37.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-2021-3516 | — | < 2.9.7-3.31.1 | 2.9.7-3.31.1 | Jun 1, 2021 | There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability. | ||
| CVE-2021-3517 | — | < 2.9.7-3.31.1 | 2.9.7-3.31.1 | May 19, 2021 | There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely | ||
| CVE-2021-3518 | — | < 2.9.7-3.31.1 | 2.9.7-3.31.1 | May 18, 2021 | There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability. | ||
| CVE-2021-3537 | — | < 2.9.7-3.34.1 | 2.9.7-3.34.1 | May 14, 2021 | A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the applicat |
- 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-3.37.1fixed 2.9.7-3.37.1
A flaw was found in libxml2. Exponential entity expansion attack its possible bypassing all existing protection mechanisms and leading to denial of service.
- CVE-2021-3516Jun 1, 2021affected < 2.9.7-3.31.1fixed 2.9.7-3.31.1
There's a flaw in libxml2's xmllint in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by xmllint could trigger a use-after-free. The greatest impact of this flaw is to confidentiality, integrity, and availability.
- CVE-2021-3517May 19, 2021affected < 2.9.7-3.31.1fixed 2.9.7-3.31.1
There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11. An attacker who is able to supply a crafted file to be processed by an application linked with the affected functionality of libxml2 could trigger an out-of-bounds read. The most likely
- CVE-2021-3518May 18, 2021affected < 2.9.7-3.31.1fixed 2.9.7-3.31.1
There's a flaw in libxml2 in versions before 2.9.11. An attacker who is able to submit a crafted file to be processed by an application linked with libxml2 could trigger a use-after-free. The greatest impact from this flaw is to confidentiality, integrity, and availability.
- CVE-2021-3537May 14, 2021affected < 2.9.7-3.34.1fixed 2.9.7-3.34.1
A vulnerability found in libxml2 in versions before 2.9.11 shows that it did not propagate errors while parsing XML mixed content, causing a NULL dereference. If an untrusted XML document was parsed in recovery mode and post-validated, the flaw could be used to crash the applicat