suse/python-libxml2&distro=SUSE Linux Enterprise Server 12 SP5

Vulnerabilities (21)

• CVE-2024-34459May 13, 2024
  affected < 2.9.4-46.75.1fixed 2.9.4-46.75.1

  An issue was discovered in xmllint (from libxml2) before 2.11.8 and 2.12.x before 2.12.7. Formatting error messages with xmllint --htmlout can result in a buffer over-read in xmlHTMLPrintFileContext in xmllint.c.

• CVE-2024-25062Feb 4, 2024
  affected < 2.9.4-46.71.1fixed 2.9.4-46.71.1

  An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free.

• CVE-2023-45322Oct 6, 2023
  affected < 2.9.4-46.68.2fixed 2.9.4-46.68.2

  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, 2023
  affected < 2.9.4-46.65.1fixed 2.9.4-46.65.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, 2023
  affected < 2.9.4-46.62.1fixed 2.9.4-46.62.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, 2023
  affected < 2.9.4-46.62.1fixed 2.9.4-46.62.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, 2022
  affected < 2.9.4-46.59.3fixed 2.9.4-46.59.3

  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, 2022
  affected < 2.9.4-46.59.3fixed 2.9.4-46.59.3

  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, 2022
  affected < 2.9.4-46.59.3fixed 2.9.4-46.59.3

  Possible cross-site scripting vulnerability in libxml after commit 960f0e2.

• CVE-2022-29824May 3, 2022
  affected < 2.9.4-46.54.3fixed 2.9.4-46.54.3

  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, 2022
  affected < 2.9.4-46.49.1fixed 2.9.4-46.49.1

  valid.c in libxml2 before 2.9.13 has a use-after-free of ID and IDREF attributes.

• CVE-2021-3541Jul 9, 2021
  affected < 2.9.4-46.46.1fixed 2.9.4-46.46.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, 2021
  affected < 2.9.4-46.40.1fixed 2.9.4-46.40.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, 2021
  affected < 2.9.4-46.40.1fixed 2.9.4-46.40.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, 2021
  affected < 2.9.4-46.40.1fixed 2.9.4-46.40.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, 2021
  affected < 2.9.4-46.43.1fixed 2.9.4-46.43.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

• CVE-2020-24977Sep 3, 2020
  affected < 2.9.4-46.34.1fixed 2.9.4-46.34.1

  GNOME project libxml2 v2.9.10 has a global buffer over-read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c. The issue has been fixed in commit 50f06b3e.

• CVE-2020-7595Jan 21, 2020
  affected < 2.9.4-46.34.1fixed 2.9.4-46.34.1

  xmlStringLenDecodeEntities in parser.c in libxml2 2.9.10 has an infinite loop in a certain end-of-file situation.

• CVE-2019-20388Jan 21, 2020
  affected < 2.9.4-46.34.1fixed 2.9.4-46.34.1

  xmlSchemaPreRun in xmlschemas.c in libxml2 2.9.10 allows an xmlSchemaValidateStream memory leak.

• CVE-2019-19956Dec 24, 2019
  affected < 2.9.4-46.34.1fixed 2.9.4-46.34.1

  xmlParseBalancedChunkMemoryRecover in parser.c in libxml2 before 2.9.10 has a memory leak related to newDoc->oldNs.