# If you’ve deployed anything since 2015, I have bad news...

## Executive summary

A rapid sequence of security vulnerabilities—affecting CDN delivery, Java JVM implementation, and Nginx HTTP2 protocol—demonstrated significant risks to deployed internet infrastructure. Attacks included a JavaScript injection via Optimizely, a Remote Code Execution (RCE) bug in Java related to B64 decoding on specific server chips, and a decade-old flaw in Nginx's flow control mechanism, which allowed command execution.

## Key takeaways

- Optimizely CDN Compromise: A bug in the Optimizely signup flow allowed attackers to inject custom JavaScript into other customers' projects, leading to malware distribution across 178 major websites (e.g., CNN, BBC, Zoom). The payload was used to skim cards and steal crypto, resulting in a reported loss of $7,500.
- Java RCE via B64 Decoding: A security firm (Khif) disclosed a Remote Code Execution bug in Java itself. The vulnerability affects newer Intel or AMD servers using the JVM's handwritten assembly version (which utilizes AVX 512) and is triggered by malformed B64 strings, allowing RCE on systems like Jira, Confluence, and Jenkins.
- Nginx Flow Control Vulnerability: A bug in Nginx, related to HTTP2 flow control, allows an attacker to exceed the 2GB credit limit. This causes an unsigned integer counter to underflow and wrap around, leading to a buffer overflow and subsequent command execution.

## Technical details

- Java JVM Vulnerability: The Java vulnerability is a math bug in the JVM's B64 decoding implementation. If a short string with messed up padding is provided, the JVM writes 62 bytes past the end of the buffer, leading to RCE. It specifically affects Java 17 and up.
- Nginx RCE Mechanism: The Nginx bug exploits the flow control mechanism. By canceling requests after maxing out credit, the counter wraps around (underflows) from a large positive number to a negative number, which is then read as a length, causing a buffer overflow and memory corruption.
- AI Design Canvas (Paper): The sponsor, Paper, is a design tool that provides a 'design canvas' built on real HTML and CSS, allowing coding agents (Claude, Cursor, Codecs) to read and write directly to the UI, eliminating translation layers.

## Practical implications

- Organizations running Java 17+ on newer Intel/AMD hardware must audit their B64 decoding processes and monitor for signs of buffer overflow exploitation.
- Web services relying on Nginx must be aware of the HTTP2 flow control limits and ensure proper configuration to prevent resource exhaustion attacks.
- The use of third-party CDNs and AB testing tools requires rigorous security auditing, as demonstrated by the Optimizely incident.

## Topics

Web Security, Remote Code Execution (RCE), Java, Nginx, CI/CD, AI Development, Optimizely, Khif, Zint, Paper

Source: https://www.youtube.com/watch?v=rMaMe32qQkA
