<?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-0325</id>
    <title>An update for varnish is now available for HCE 2.0</title>
    <severity>Important</severity>
    <release>HCE 2.0</release>
    <issued date="2025-12-09 06:53:38"/>
    <updated date="2025-12-09 06:53:38"/>
    <references>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-47905" id="CVE-2025-47905" title="CVE-2025-47905 Base Score: 5.4 Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N" type="cve"/>
      <reference href="https://nvd.nist.gov/vuln/detail/CVE-2025-8671" id="CVE-2025-8671" title="CVE-2025-8671 Base Score: 7.5 Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H" type="cve"/>
    </references>
    <description>Security Fix(es):

Varnish Cache before 7.6.3 and 7.7 before 7.7.1, and Varnish Enterprise before 6.0.13r14, allow client-side desync via HTTP/1 requests, because the product incorrectly permits CRLF to be skipped to delimit chunk boundaries. (CVE-2025-47905)

A mismatch caused by client-triggered server-sent stream resets between HTTP/2 specifications and the internal architectures of some HTTP/2 implementations may result in excessive server resource consumption leading to denial-of-service (DoS).  By opening streams and then rapidly triggering the server to reset them—using malformed frames or flow control errors—an attacker can exploit incorrect stream accounting. Streams reset by the server are considered closed at the protocol level, even though backend processing continues. This allows a client to cause the server to handle an unbounded number of concurrent streams on a single connection. This CVE will be updated as affected product details are released. (CVE-2025-8671)
</description>
    <pkglist>
      <collection short="HCE 2.0" package="varnish">
        <name>HCE 2.0</name>
        <package arch="x86_64" name="varnish" version="7.4.3" release="1.r3.hce2">
          <filename>varnish-7.4.3-1.r3.hce2.x86_64.rpm</filename>
        </package>
        <package arch="x86_64" name="varnish-devel" version="7.4.3" release="1.r3.hce2">
          <filename>varnish-devel-7.4.3-1.r3.hce2.x86_64.rpm</filename>
        </package>
        <package arch="noarch" name="varnish-help" version="7.4.3" release="1.r3.hce2">
          <filename>varnish-help-7.4.3-1.r3.hce2.noarch.rpm</filename>
        </package>
        <package arch="aarch64" name="varnish" version="7.4.3" release="1.r3.hce2">
          <filename>varnish-7.4.3-1.r3.hce2.aarch64.rpm</filename>
        </package>
        <package arch="aarch64" name="varnish-devel" version="7.4.3" release="1.r3.hce2">
          <filename>varnish-devel-7.4.3-1.r3.hce2.aarch64.rpm</filename>
        </package>
      </collection>
    </pkglist>
  </update>
