☠️
EXFILTRATING
DATA...
01010111 10110010 00101001 11000110 01101100 10011011 00010001 11100101 01000010 10101111
[ <-- BACK_TO_SEARCH ]

CVE-2025-4820

CVE-2025-4820 Supply Chain Attack in Cloudflare
📅 PUBLISHED: 2025-06-18 15:45 UTC 🔄 UPDATED: 2026-09-23 20:31 UTC
[ OFFICIAL PATCH DEPLOYED ↓ ] FIX: LIKELY — 2 independent sources confirm fix
[ DEFENSE PATCH ↓ ]
💣 PoC: None
👁️
Proof of Concept - Indicates if functional exploit code is publicly available, drastically increasing the risk of immediate attacks.
🎯 EPSS: 0.86%
👁️
0.86% probability
21.6× above the median CVE
Tier: ELEVATED
30-day exploitation window · FIRST.org · updated daily
Country: USA License: Freemium
Patch available — upgrade to latest release
CVSS SEVERITY SCALE
9.0–10.0 CRITICAL
7.0–8.9 HIGH
4.0–6.9 MEDIUM
0.1–3.9 LOW
0.0 NONE
5.3
THREAT LEVEL
■ tracking this CVE ✓ independent patch confirmation ⧗ same-origin mirror (GHSA) ⚠ active exploitation verification policy →

Executive Summary

CVE-2025-4820 is a vulnerability in Cloudflare's QUIC implementation, quiche, that allows an unauthenticated remote attacker to manipulate the victim's congestion control state. By sending crafted ACK frames, an attacker can cause the victim to grow its congestion window beyond the path's actual capacity, leading to potential data over-sending and network congestion. The vulnerability has a CVSS score of 5.3 (Medium) and is patched in quiche version 0.24.4. The EPSS score is 0.0%, indicating low exploitation likelihood at this time.

⚡ AUTOMATE YOUR CVE INTELLIGENCE

This record — and 170,000+ others — are available via the ValtersIT API. One endpoint replaces five: NVD + GitHub CVE + CISA KEV + EPSS + Nuclei + Exploit-DB, unified.

›Patch confidence — UNVERIFIED to CONFIRMED, cross-referenced NVD + RHSA + Debian
›Exploit & PoC — poc_status, poc_url, has_exploit. Not in NVD.
›Shodan dorks — ready-made queries to find exposed vulnerable systems
›Detection rules — YARA · Wazuh · Elastic (all plans) · Sigma (Pro)
›pending_fields — know exactly which of 7 fields NVD hasn't processed yet
›Free backfill — data incomplete when you paid? Re-check within 30 days = 0 credits
PAYG €0.08/lookup Standard €19/mo (was €29) · 5k credits Pro €65/mo (was €99) · 20k credits FOUNDING PRICE · LOCKED FOR LIFE · ENDS 31 DEC 2026
[ FROM €19/MO ]
Free sandbox key available
No signup required

Supply Chain & Package Security

This vulnerability affects the quiche library, which is a Rust-based implementation of the QUIC protocol. Organizations using quiche in their applications should update to version 0.24.4 or later. The library is distributed via crates.io and GitHub. Users should verify their dependency versions and ensure they are not using vulnerable versions.

CVSS Breakdown & Threat Level

  • CVSS Score: 5.3 (Medium)
  • Attack Vector: Network (AV:N)
  • Attack Complexity: Low (AC:L)
  • Privileges Required: None (PR:N)
  • User Interaction: None (UI:N)
  • Scope: Unchanged (S:U)
  • Confidentiality Impact: None (C:N)
  • Integrity Impact: Low (I:L)
  • Availability Impact: None (A:N)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

The vulnerability allows an attacker to manipulate the congestion window, potentially causing the victim to send data at a rate faster than the path supports. This could lead to network congestion and performance degradation, but does not directly compromise data confidentiality or availability.

Deep Dive & Mechanics

The vulnerability lies in how quiche handles ACK frames during congestion control. According to RFC 9000 Section 21.4, an opportunistic ACK attack occurs when an attacker sends ACK frames that acknowledge data that was not actually received, causing the sender to incorrectly grow its congestion window. In quiche, the congestion window growth logic did not properly validate ACK frames against this attack vector.

When an attacker completes a QUIC handshake and initiates a congestion-controlled data transfer, they can send crafted ACK frames that appear to acknowledge more data than was actually received. The victim's quiche implementation then incorrectly increases the congestion window, allowing more bytes in flight than the path can support. This can lead to packet loss, retransmissions, and overall network performance degradation.

The fix in quiche 0.24.4 adds validation of ACK frames to ensure they comply with RFC 9000 Section 21.4, preventing the opportunistic ACK attack from manipulating the congestion window.

Vulnerable vs. Patched Code

The vulnerable code likely resides in the congestion control module, specifically in the logic that processes ACK frames and updates the congestion window. The patched version adds checks to validate that ACK frames do not acknowledge data beyond what was actually sent or received.

Vulnerable Code (Conceptual):

// Vulnerable: No validation of ACK frames
fn on_ack_received(&mut self, ack: &AckFrame) {
    let bytes_acked = ack.largest_acked - ack.first_acked + 1;
    self.congestion_window += bytes_acked * MSS;
}

Patched Code (Conceptual):

// Patched: Validate ACK frames against RFC 9000 Section 21.4
fn on_ack_received(&mut self, ack: &AckFrame, sent_packets: &SentPacketMap) {
    // Validate that the ACK acknowledges only packets that were actually sent
    for packet_num in ack.first_acked..=ack.largest_acked {
        if !sent_packets.contains(packet_num) {
            // Ignore ACK as it acknowledges unsent data
            return;
        }
    }
    let bytes_acked = ack.largest_acked - ack.first_acked + 1;
    self.congestion_window += bytes_acked * MSS;
}

Exploitation & Lab Setup

Red Team

To exploit this vulnerability, an attacker would need to:

  1. Complete a QUIC handshake with the victim.
  2. Initiate a congestion-controlled data transfer.
  3. Send crafted ACK frames that acknowledge more data than was actually received.

Proof of Concept (Conceptual):

import socket
import struct

# Assume QUIC connection established
def send_opportunistic_ack(sock, victim_addr, largest_acked, first_acked):
    # Craft ACK frame with inflated acknowledgment
    ack_frame = struct.pack('!BBHH', 0x02, 0x00, largest_acked, first_acked)
    sock.sendto(ack_frame, victim_addr)

# Example usage
sock = socket.socket(socket.AF_INET, socket.SOCK_DGRAM)
send_opportunistic_ack(sock, ('victim_ip', 443), 1000, 1)

Blue Team

To detect exploitation attempts:

  1. Monitor for unusual ACK patterns, such as ACKs acknowledging packets that were never sent.
  2. Implement rate limiting on ACK processing.
  3. Use network monitoring tools to detect abnormal congestion window growth.

Detection Script (Python):

import pyshark

def detect_opportunistic_ack(pcap_file):
    cap = pyshark.FileCapture(pcap_file, display_filter='quic')
    for packet in cap:
        if hasattr(packet, 'quic'):
            ack_ranges = packet.quic.ack_ranges
            # Check for suspicious ACK ranges
            for ack_range in ack_ranges:
                if ack_range.largest_acked - ack_range.first_acked > 1000:
                    print(f"Suspicious ACK: {ack_range}")

Indicators of Compromise (IOCs)

  • Network IOCs:

    • Unusual ACK frames with large acknowledgment ranges.
    • Rapid congestion window growth in QUIC connections.
    • Increased packet loss and retransmissions.
  • Host IOCs:

    • Quiche version < 0.24.4.
    • Logs showing unexpected congestion window increases.
  • File IOCs:

    • Hash of vulnerable quiche library: (SHA256 of quiche 0.24.3 or earlier)

Detection Engineering

YARA Rule

rule CVE_2025_4820_quiche_opportunistic_ack {
    meta:
        description = "Detects quiche versions vulnerable to CVE-2025-4820"
        author = "Valters IT"
        date = "2025-04-10"
        reference = "https://nvd.nist.gov/vuln/detail/CVE-2025-4820"
    strings:
        $vuln_version = "quiche 0.24." ascii wide nocase
        $patch_version = "quiche 0.24.4" ascii wide nocase
    condition:
        $vuln_version and not $patch_version
}

Sigma Rule

title: CVE-2025-4820 - Opportunistic ACK Attack Detection
id: 8a9b7c6d-5e4f-3a2b-1c0d-9e8f7a6b5c4d
status: experimental
description: Detects potential exploitation of CVE-2025-4820 via abnormal ACK patterns
author: Valters IT
date: 2025-04-10
logsource:
    category: network
    product: quic
detection:
    selection:
        quic.ack_ranges.largest_acked - quic.ack_ranges.first_acked > 1000
    condition: selection
falsepositives:
    - Legitimate high-throughput transfers
level: medium

Suricata Rule

alert udp any any -> any 443 (msg:"CVE-2025-4820 - Opportunistic ACK Attack"; content:"|02 00|"; offset:0; depth:2; byte_test:2,>,1000,2,relative; sid:1000001; rev:1;)

Remediation & Mitigation

  1. Immediate Action: Update quiche to version 0.24.4 or later.
  2. Network Mitigation: Implement rate limiting on ACK processing and monitor for abnormal congestion window growth.
  3. Configuration: Ensure QUIC implementations validate ACK frames against RFC 9000 Section 21.4.
  4. Monitoring: Deploy detection rules (YARA, Sigma, Suricata) to identify exploitation attempts.
  5. Long-term: Review and test all QUIC implementations for similar vulnerabilities.

Valters IT
Securing Digital Frontiers

◈ SOURCE Analysis & enrichment: valtersit.com/cve/CVE-2025-4820/ · CVE data: NVD/MITRE (public domain) · © 2026 ValtersIT Hub
>_ SYSTEM_CORE: INTEL_ACTIVE
90% TEAM-CURATED // 10% AUTOMATED INGESTION.
ALL PATCH REFERENCES AND VERSION DATA SOURCED FROM NVD + OSV OFFICIAL REGISTRIES.