<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cloud Security on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/cloud-security/</link><description>Recent content in Cloud Security on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Tue, 23 Jun 2026 12:12:16 +0200</lastBuildDate><atom:link href="https://hackingpassion.com/tags/cloud-security/index.xml" rel="self" type="application/rss+xml"/><item><title>Google Told the Researcher Nice Catch Then Refused to Pay and Never Fixed It</title><link>https://hackingpassion.com/configconfusion-google-no-bounty/</link><pubDate>Tue, 23 Jun 2026 12:12:16 +0200</pubDate><guid>https://hackingpassion.com/configconfusion-google-no-bounty/</guid><description>&lt;p>Google told a security researcher his bug was a nice catch, lined up his payout, then eleven days later called it harmless and refused to pay a cent. The flaw he reported lets anyone with basic Kubernetes access take over a complete Google Cloud organization in about five seconds, with three lines of text and no special permissions at all. Months on, it still is not fixed. He named it &lt;strong>ConfigConfusion&lt;/strong>.&lt;/p></description></item><item><title>Google API Keys Keep Working for 23 Minutes After You Delete Them</title><link>https://hackingpassion.com/google-api-key-23-minutes/</link><pubDate>Sat, 23 May 2026 15:04:37 +0200</pubDate><guid>https://hackingpassion.com/google-api-key-23-minutes/</guid><description>&lt;p>Google tells you the key is gone. It keeps working for &lt;strong>23 more minutes&lt;/strong>. When you delete a Google API key, a dialog appears that says the following: &lt;em>&amp;ldquo;Once deleted, it can no longer be used to make API requests.&amp;rdquo;&lt;/em> That is the message. It is printed there by Google, presented as fact at the exact moment you think the risk is gone. It is not true.&lt;/p>
&lt;p>Security researcher &lt;strong>Joe Leon&lt;/strong> at &lt;strong>Aikido Security&lt;/strong> spent two days testing what actually happens after a key is deleted. He created keys, deleted them, and kept firing authenticated requests at Google&amp;rsquo;s servers at three to five per second until no valid response came back. He ran ten separate trials. The shortest window before a deleted key fully stopped working was nearly &lt;strong>eight minutes&lt;/strong>. The median was &lt;strong>sixteen minutes&lt;/strong>. The longest was just under &lt;strong>twenty-three minutes&lt;/strong>. During all of that time, the key was authenticating successfully on Google&amp;rsquo;s infrastructure. A deleted key. Still working.&lt;/p></description></item><item><title>Microsoft Bing CVSS 10.0: CVE-2026-33819 Remote Code Execution Explained</title><link>https://hackingpassion.com/bing-rce-cve-2026-33819/</link><pubDate>Sat, 25 Apr 2026 11:10:39 +0200</pubDate><guid>https://hackingpassion.com/bing-rce-cve-2026-33819/</guid><description>&lt;p>&lt;strong>Bing had a CVSS 10.0 vulnerability&lt;/strong> in its backend infrastructure, the same infrastructure that powers Edge, Windows Search, and Copilot integrations across Microsoft&amp;rsquo;s ecosystem. Microsoft fixed it on March 10 without saying a word publicly. The CVE showed up six weeks later, on April 23. Nobody outside the company knew this had been sitting in the infrastructure that hundreds of millions of people use every day.&lt;/p>
&lt;p>The CVE number is &lt;strong>2026-33819&lt;/strong>. The vulnerability class is &lt;strong>deserialization of untrusted data&lt;/strong>, and the idea behind it is simpler than it sounds.&lt;/p></description></item><item><title>VoidLink: 88,000 Lines of AI-Built Malware in 6 Days</title><link>https://hackingpassion.com/voidlink-ai-malware/</link><pubDate>Wed, 21 Jan 2026 15:24:02 +0100</pubDate><guid>https://hackingpassion.com/voidlink-ai-malware/</guid><description>&lt;p>One developer just built 88,000 lines of advanced malware in six days using AI. A single person with an AI coding assistant created a framework sophisticated enough to target AWS, Azure, Google Cloud, Alibaba, Tencent, Kubernetes pods, and Docker containers. 🧐&lt;/p>
&lt;p>Check Point revealed VoidLink on January 20, 2026. A Linux malware framework designed to compromise cloud infrastructure. The malware detects where it runs and changes its behavior based on what it finds.&lt;/p></description></item><item><title>Two Missing Characters Nearly Compromised the AWS Supply Chain</title><link>https://hackingpassion.com/aws-supply-chain-vulnerability/</link><pubDate>Sat, 17 Jan 2026 13:49:16 +0100</pubDate><guid>https://hackingpassion.com/aws-supply-chain-vulnerability/</guid><description>&lt;p>Netflix. Twitch. iCloud. The servers of the CIA and NSA. 30% of all cloud infrastructure worldwide runs on Amazon Web Services. Two missing characters in a regex filter nearly compromised all of it. 😬&lt;/p>
&lt;p>A &lt;code>^&lt;/code> at the start and a &lt;code>$&lt;/code> at the end. That&amp;rsquo;s what was missing from a security filter, and that&amp;rsquo;s all it would have taken for attackers to inject malicious code into the AWS JavaScript SDK.&lt;/p></description></item></channel></rss>