<?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>HCE2-SA-2025-0308</id>
    <title>An update for libtiff is now available for HCE 2.0</title>
    <severity>Important</severity>
    <release>HCE 2.0</release>
    <issued date="2025-12-09 06:53:37"/>
    <updated date="2025-12-09 06:53:37"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-9165" id="CVE-2025-9165" title="CVE-2025-9165 Base Score: 2.5 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-9900" id="CVE-2025-9900" title="CVE-2025-9900 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-2025-8851" id="CVE-2025-8851" title="CVE-2025-8851 Base Score: 5.3 Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-8534" id="CVE-2025-8534" title="CVE-2025-8534 Base Score: 2.5 Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L" type="cve"/>
    </references>
    <description>Security Fix(es):

A flaw has been found in LibTIFF 4.7.0. This affects the function _TIFFmallocExt/_TIFFCheckRealloc/TIFFHashSetNew/InitCCITTFax3 of the file tools/tiffcmp.c of the component tiffcmp. Executing manipulation can lead to memory leak. The attack is restricted to local execution. This attack is characterized by high complexity. It is indicated that the exploitability is difficult. The exploit has been published and may be used. There is ongoing doubt regarding the real existence of this vulnerability. This patch is called ed141286a37f6e5ddafb5069347ff5d587e7a4e0. It is best practice to apply a patch to resolve this issue. A researcher disputes the security impact of this issue, because &quot;this is a memory leak on a command line tool that is about to exit anyway&quot;. In the reply the project maintainer declares this issue as &quot;a simple _x27;bug_x27; when leaving the command line tool and (...) not a security issue at all&quot;. (CVE-2025-9165)

A flaw was found in Libtiff. This vulnerability is a &quot;write-what-where&quot; condition, triggered when the library processes a specially crafted TIFF image file.

By providing an abnormally large image height value in the file_x27;s metadata, an attacker can trick the library into writing attacker-controlled color data to an arbitrary memory location. This memory corruption can be exploited to cause a denial of service (application crash) or to achieve arbitrary code execution with the permissions of the user. (CVE-2025-9900)

A vulnerability was determined in LibTIFF up to 4.5.1. Affected by this issue is the function readSeparateStripsetoBuffer of the file tools/tiffcrop.c of the component tiffcrop. The manipulation leads to stack-based buffer overflow. Local access is required to approach this attack. The patch is identified as 8a7a48d7a645992ca83062b3a1873c951661e2b3. It is recommended to apply a patch to fix this issue. (CVE-2025-8851)

A vulnerability classified as problematic was found in libtiff 4.6.0. This vulnerability affects the function PS_Lvl2page of the file tools/tiff2ps.c of the component tiff2ps. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 6ba36f159fd396ad11bf6b7874554197736ecc8b. It is recommended to apply a patch to fix this issue. One of the maintainers explains, that &quot;[t]his error only occurs if DEFER_STRILE_LOAD (defer-strile-load:BOOL=ON) or TIFFOpen( .. &quot;rD&quot;) option is used.&quot; (CVE-2025-8534)
</description>
    <pkglist>
      <collection short="HCE 2.0" package="libtiff">
        <name>HCE 2.0</name>
        <package arch="x86_64" name="libtiff" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-4.3.0-9.r31.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="libtiff-devel" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-devel-4.3.0-9.r31.hce2.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="libtiff-help" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-help-4.3.0-9.r31.hce2.noarch.rpm</filename>
        </package>
        <package arch="x86_64" name="libtiff-static" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-static-4.3.0-9.r31.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="libtiff-tools" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-tools-4.3.0-9.r31.hce2.x86_64.rpm</filename>
        </package>
        <package arch="aarch64" name="libtiff" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-4.3.0-9.r31.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="libtiff-devel" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-devel-4.3.0-9.r31.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="libtiff-static" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-static-4.3.0-9.r31.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="libtiff-tools" version="4.3.0" release="9.r31.hce2">
          <filename>libtiff-tools-4.3.0-9.r31.hce2.aarch64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
