{"id":11562,"date":"2026-09-04T18:53:42","date_gmt":"2026-09-04T10:53:42","guid":{"rendered":"https:\/\/www.54iter.cn\/?vuln=cve-2026-63075"},"modified":"2026-09-04T18:53:42","modified_gmt":"2026-09-04T10:53:42","slug":"cve-2026-63075","status":"publish","type":"vuln","link":"https:\/\/www.54iter.cn\/?vuln=cve-2026-63075","title":{"rendered":"CVE-2026-63075 [HIGH] &#8211; Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly\nsends ack-e"},"content":{"rendered":"<p>Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly<br \/>\nsends ack-eliciting packets while not acknowledging ACK-only responses, the<br \/>\nQUIC stack can retain ACK-only packet metadata for the lifetime of the<br \/>\nconnection.<\/p>\n<p>Impact summary: A remote peer that can complete a QUIC handshake can<br \/>\ncause connection-scoped memory growth which may lead to Denial of Service<br \/>\nthrough memory exhaustion, especially with sustained traffic or many concurrent<br \/>\nQUIC connections.<\/p>\n<p>CWE: CWE-770: Allocation of Resources Without Limits or Throttling<\/p>\n<p>Description: When the OpenSSL QUIC stack sends an ACK-only packet,<br \/>\nthere is no requirement by the QUIC protocol that the peer will acknowledge<br \/>\nthat ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL<br \/>\nimplementation stores the metadata about the ACK frames regardless.<br \/>\nIn and of itself that&#8217;s ok, but if a malicious peer establishes a connection, and<br \/>\nthen drives the connection such that ACK-only packets are forced from the<br \/>\nOpenSSL implementation peer (i.e., by sending numerous PING frames),<br \/>\nand then withholding any subsequent acks for ack-eliciting data, like<br \/>\nlegitimate data, said malicious peer can force inappropriate memory growth<br \/>\non the OpenSSL peer, potentially leading to a Denial of Service.<\/p>\n<p>The fix is to ensure that we account for the transmission of the ACK-only<br \/>\npacket in the packet histories high and low watermark without actually storing<br \/>\nthe ACK-only packet metadata itself.<\/p>\n<p>FIPS impact: no<br \/>\nThe OpenSSL FIPS module is not affected as the QUIC code is<br \/>\noutside the FIPS module boundary.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly<br \/>\nsends ack-eliciting packets while not acknowledging ACK-only responses, the<br \/>\nQUIC stack can retain ACK-only packet metadat<\/p>\n","protected":false},"template":"","meta":[],"categories":[],"tags":[],"class_list":["post-11562","vuln","type-vuln","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln\/11562","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/vuln"}],"about":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=\/wp\/v2\/types\/vuln"}],"wp:attachment":[{"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=11562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=11562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.54iter.cn\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=11562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}