<?xml version="1.0" encoding="utf-8"?>
  <?xml-stylesheet type="text/xsl" href="sa-render.xsl"?>
  <update from="huaweicloud.com" type="security" status="stable" version="1">
    <id>HCE1-SA-2022-0019</id>
    <title>An update for libxml2 is now available for HCE 1.1</title>
    <severity>Important</severity>
    <release>HCE 1.1</release>
    <issued date="2022-10-18 09:08:05"/>
    <updated date="2022-10-18 09:08:05"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2017-9047" id="CVE-2017-9047" title="CVE-2017-9047 Base Score: 7.5 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2021-3518" id="CVE-2021-3518" title="CVE-2021-3518 Base Score: 8.8 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2017-16932" id="CVE-2017-16932" title="CVE-2017-16932 Base Score: 7.5 Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2022-29824" id="CVE-2022-29824" title="CVE-2022-29824 Base Score: 6.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

A buffer overflow was discovered in libxml2 20904-GITv2.9.4-16-g0741801. The function xmlSnprintfElementContent in valid.c is supposed to recursively dump the element content definition into a char buffer 'buf' of size 'size'. The variable len is assigned strlen(buf). If the content-&gt;type is XML_ELEMENT_CONTENT_ELEMENT, then (i) the content-&gt;prefix is appended to buf (if it actually fits) whereupon (ii) content-&gt;name is written to the buffer. However, the check for whether the content-&gt;name actually fits also uses 'len' rather than the updated buffer length strlen(buf). This allows us to write about &quot;size&quot; many bytes beyond the allocated memory. This vulnerability causes programs that use libxml2, such as PHP, to crash. (CVE-2017-9047)

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-3518)

parser.c in libxml2 before 2.9.5 does not prevent infinite recursion in parameter entities. (CVE-2017-16932)

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 using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well. (CVE-2022-29824)
</description>
    <pkglist>
      <collection short="HCE 1.1" package="libxml2">
        <name>HCE 1.1</name>
        <package arch="x86_64" name="libxml2" version="2.9.1" release="6.hce1c.8">
          <filename>libxml2-2.9.1-6.hce1c.8.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="libxml2-devel" version="2.9.1" release="6.hce1c.8">
          <filename>libxml2-devel-2.9.1-6.hce1c.8.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="libxml2-python" version="2.9.1" release="6.hce1c.8">
          <filename>libxml2-python-2.9.1-6.hce1c.8.x86_64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
