VYPR

rpm package

suse/python-libxml2&distro=SUSE Linux Enterprise Server for SAP Applications 12 SP4

pkg:rpm/suse/python-libxml2&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP4

Vulnerabilities (11)

  • 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-3516Jun 1, 2021
    affected < 2.9.4-46.43.1fixed 2.9.4-46.43.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.43.1fixed 2.9.4-46.43.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.43.1fixed 2.9.4-46.43.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-2017-16932HigNov 23, 2017
    affected < 2.9.4-46.54.3fixed 2.9.4-46.54.3

    parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities.

  • CVE-2016-9318MedNov 16, 2016
    affected < 2.9.4-46.20.1fixed 2.9.4-46.20.1

    libxml2 2.9.4 and earlier, as used in XMLSec 1.2.23 and earlier and other products, does not offer a flag directly indicating that the current document may be read but other files may not be opened, which makes it easier for remote attackers to conduct XML External Entity (XXE) a