<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Memory-Amplification on CuraSec</title><link>https://curasec.metacog.co.kr/tags/memory-amplification/</link><description>Recent content in Memory-Amplification on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 22 Oct 2026 15:52:23 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/memory-amplification/index.xml" rel="self" type="application/rss+xml"/><item><title>QPACK Flaws Allow Unauthenticated DoS and 4,000x Memory Amplification on HTTP/3 Servers</title><link>https://curasec.metacog.co.kr/insights/2026-10-22-new-qpack-flaws-can-crash-http-3-servers-trigger-up-to-4-000/</link><pubDate>Thu, 22 Oct 2026 15:52:23 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-10-22-new-qpack-flaws-can-crash-http-3-servers-trigger-up-to-4-000/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Act:&lt;/strong> A public PoC now exists for crashing HTTP/3 servers with a single unauthenticated request via QPACK header expansion; audit whether HTTP/3 is enabled on your edge servers (nginx, Caddy, Envoy, etc.) and disable it or apply vendor patches as they arrive — exposure is immediate with PoC code released.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> No active exploitation campaign is reported, but the public PoC lowers the bar quickly; build detections for anomalous single-connection HTTP/3 sessions paired with server OOM events or abrupt restarts, and add HTTP/3 header-decompression anomalies to your edge-device monitoring coverage.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item></channel></rss>