Rankiteo Logo
Rankiteo
Leader in Cyber Underwriting
Loading...
NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop
WindowsmacOSLinux
Download
Analyze » Cloudflare » CLO1773147283

Incident Score: Analysis & Impact (CLO1773147283)

The details regarding individual company incidents & reports gives you full view from every side.

Rankiteo Score Impact Analysis

Rankiteo Incident Impact-3
Company Score Before Incident638 / 1000
Company Score After Incident635 / 1000
INCIDENT NUMBERCLO1773147283
Type of Cyber IncidentVulnerability
ATTACK VECTORExploitation of improper HTTP request handling and cache key generation in Pingora proxy framework
DATA EXPOSEDMalicious content delivery, Phishing pages,...
INCIDENT DATE30/04/2025
STATUSResolved

Key Highlights From The Incident Analysis

  • Timeline of Cloudflare's Vulnerability and lateral movement inside company's environment.
  • Overview of affected data sets, including SSNs and PHI, and why they materially increase incident severity.
  • How Rankiteo’s incident engine converts technical details into a normalized incident score.
  • How this cyber incident impacts Cloudflare Rankiteo cyber scoring and cyber rating.
  • Rankiteo’s MITRE ATT&CK correlation analysis for this incident, with associated confidence level.

Full Incident Analysis Transcript

In this Rankiteo incident briefing, we review the Cloudflare breach identified under incident ID CLO1773147283.

The analysis begins with a detailed overview of Cloudflare's information like the linkedin page: https://www.linkedin.com/company/cloudflare, the number of followers: 1140726, the industry type: Computer and Network Security and the number of employees: 6899 employees

After the initial compromise, the video explains how Rankiteo's incident engine converts technical details into a normalized incident score. The incident score before the incident was 638 and after the incident was 635 with a difference of -3 which is could be a good indicator of the severity and impact of the incident.

In the next step of the video, we will analyze in more details the incident and the impact it had on Cloudflare and their customers.

Cloudflare recently reported "Cloudflare Patches Critical Pingora Flaws Enabling HTTP Request Smuggling and Cache Poisoning", a noteworthy cybersecurity incident.

In May 2025, Cloudflare disclosed multiple high-severity vulnerabilities in Pingora, its Rust-based proxy framework, which could allow attackers to smuggle HTTP requests, poison caches, and deliver malicious content at scale.

The disruption is felt across the environment, affecting Pingora proxy framework (versions before 0.8.0), and exposing Malicious content delivery, Phishing pages and Malware payloads.

In response, teams activated the incident response plan, moved swiftly to contain the threat with measures like Disabled affected Pingora components and Invalidated cached assets, and began remediation that includes Released Pingora 0.5.0+ and 0.8.0+ with fixes, Mandated draining HTTP/1.1 request bodies and Hardened HTTP message parsing per RFC 9112, while recovery efforts such as Upgraded Pingora versions and Validated cache key settings continue.

The case underscores how Resolved, teams are taking away lessons such as Importance of proper HTTP request handling, cache key generation, and multi-tenant isolation in proxy frameworks. Need for timely patching and validation of default configurations, and recommending next steps like Upgrade to Pingora ≥0.8.0, Include Host/authority in cache keys for multi-tenant deployments and Validate caching configurations, with advisories going out to stakeholders covering Organizations using Pingora advised to upgrade and validate cache key settings.

Finally, we try to match the incident with the MITRE ATT&CK framework to see if there is any correlation between the incident and the MITRE ATT&CK framework.

The MITRE ATT&CK framework is a knowledge base of techniques and sub-techniques that are used to describe the tactics and procedures of cyber adversaries. It is a powerful tool for understanding the threat landscape and for developing effective defense strategies.

MITRE ATT&CK® Correlation Analysis

Rankiteo's analysis has identified several MITRE ATT&CK tactics and techniques associated with this incident, each with varying levels of confidence based on available evidence. Under the Initial Access tactic, the analysis identified Exploit Public-Facing Application (T1190) with high confidence (90%), supported by evidence indicating exploitation of improper HTTP request handling in Pingora proxy framework. Under the Execution tactic, the analysis identified Exploitation for Client Execution (T1203) with moderate to high confidence (70%), supported by evidence indicating deliver malicious content at scale via cache poisoning. Under the Persistence tactic, the analysis identified Server Software Component: Web Shell (T1505.003) with moderate confidence (50%), supported by evidence indicating malicious content...cached and served to unrelated sites. Under the Privilege Escalation tactic, the analysis identified Exploitation for Privilege Escalation (T1068) with moderate confidence (60%), supported by evidence indicating bypass IP-based access controls via HTTP/1.0 desync. Under the Defense Evasion tactic, the analysis identified Valid Accounts (T1078) with moderate confidence (50%), supported by evidence indicating session hijacking via request smuggling and Hide Artifacts: Email Hiding Rules (T1564.008) with lower confidence (40%), supported by evidence indicating forged Host headers or paths tricking downstream servers. Under the Credential Access tactic, the analysis identified Adversary-in-the-Middle (T1557) with moderate to high confidence (70%), supported by evidence indicating session hijacking via HTTP/1.0 desync and request smuggling. Under the Discovery tactic, the analysis identified Account Discovery (T1087) with moderate confidence (50%), supported by evidence indicating cross-tenant data leaks via weak cache keys. Under the Collection tactic, the analysis identified Data from Cloud Storage (T1530) with moderate confidence (60%), supported by evidence indicating cross-tenant data leaks via weak cache keys. Under the Exfiltration tactic, the analysis identified Exfiltration Over C2 Channel (T1041) with moderate confidence (50%), supported by evidence indicating traffic redirection via request smuggling and Automated Exfiltration (T1020) with moderate confidence (60%), supported by evidence indicating malicious content delivery at scale via cache poisoning. Under the Impact tactic, the analysis identified Network Denial of Service (T1498) with lower confidence (40%), supported by evidence indicating cache poisoning enabling widespread malicious content delivery and Defacement (T1491) with moderate to high confidence (70%), supported by evidence indicating phishing pages or malware payloads served via cache poisoning. These correlations help security teams understand the attack chain and develop appropriate defensive measures based on the observed tactics and techniques.

Initial Access
Exploit Public-Facing Application (90%)
Execution
Exploitation for Client Execution (70%)
Persistence
Server Software Component: Web Shell (50%)
Privilege Escalation
Exploitation for Privilege Escalation (60%)
Defense Evasion
Valid Accounts (50%)
Hide Artifacts: Email Hiding Rules (40%)
Credential Access
Adversary-in-the-Middle (70%)
Discovery
Account Discovery (50%)
Collection
Data from Cloud Storage (60%)
Exfiltration
Exfiltration Over C2 Channel (50%)
Automated Exfiltration (60%)
Impact
Network Denial of Service (40%)
Defacement (70%)

Sources & References