InfoSecBulletin Cybersecurity for mankind
Cloudflare suffered an incident roughly 3.5 hours On November 14, 2024 impacting the majority of customers using Cloudflare Logs. Cloudflare lost about 55% of the logs normally send to customers were not sent and were lost on that incident.
Log services are crucial for network operations, helping businesses analyze traffic, troubleshoot issues, and detect threats. Cloudflare’s log service uses a tool called Logpush to process and deliver large amounts of data to customers.
B1ack’s Stash Releases 1 Million Credit Cards on a Deep Web Forum
Cisco Confirms
Salt Typhoon Exploited CVE-2018-0171 to Target U.S. Telecom Networks
AWS Key Hunter
Test this free automated tool to hunt for exposed AWS secrets
Check Point Flaw Used to Deploy ShadowPad and Ransomware
CVE-2024-12284
Citrix Issues Security Update for NetScaler Console
CISA and FBI ALERT
Ghost ransomware to breach organizations in 70 countries
Hacker chains multiple vulns to attack Palo Alto Firewall
150 Gov.t Portal affected
Black-Hat SEO Poisoning Indian “.gov.in, .ac.in” domain
CVE-2018-19410 Exposes 600 PRTG Instances in Bangladesh
Builder claims Rs 150 cr for data loss; AWS faces FIR In Bengaluru
On November 14th, a Logpush update caused a significant error. Cloudflare’s incident report revealed that the update did not direct auxiliary tools to send the collected logs. Consequently, the logs were collected but never delivered and were eventually lost when the cache was cleared.
“A misconfiguration in one part of the system caused a cascading overload in another part of the system, which was itself misconfigured. Had it been properly configured, it could have prevented the loss of logs,” Cloudflare stated in their report.
Engineers team quickly found the flaw and reverted the update, but this caused a cascading failure. The system became overwhelmed with excessive log data, including from users who hadn’t set up Logpush, worsening the problem.
Cloudflare has apologized for the loss of user data and is implementing measures to prevent future incidents, though efforts are still underway.
The loss of important log data highlights the need for thorough testing and backup measures to maintain the integrity and availability of crucial information.
