<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>CI/CD Security on HackingPassion.com : root@HackingPassion.com-[~]</title><link>https://hackingpassion.com/tags/ci/cd-security/</link><description>Recent content in CI/CD Security on HackingPassion.com : root@HackingPassion.com-[~]</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sat, 17 Jan 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://hackingpassion.com/tags/ci/cd-security/index.xml" rel="self" type="application/rss+xml"/><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>