CVE-2009-3869 is a stack-based buffer overflow in the setDiffICM function in the Abstract Window Toolkit (AWT) component of Sun Java SE / Java Runtime Environment. The issue affects JDK and JRE 5.0 before Update 22, JDK and JRE 6 before Update 17, SDK and JRE 1.3.x before 1.3.1_27, and SDK and JRE 1.4.x before 1.4.2_24. A remote attacker can trigger the flaw by supplying a crafted argument that causes improper bounds handling in setDiffICM, leading to memory corruption on the stack and potential arbitrary code execution. The issue is also identified as Sun Bug Id 6872357.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (modules/exploits/multi/browser/java_setdifficm_bof.rb) that exploits a buffer overflow vulnerability in the setDiffICM function of the Sun Java JRE (CVE-2009-3869). The exploit acts as an HTTP server, serving a malicious Java applet (CVE-2009-3869.jar) to clients who visit the server with a vulnerable Java-enabled browser. The module supports multiple platforms (Windows and Mac OS X) and architectures (x86, PPC), and can deliver any Metasploit payload that fits within the size constraints. The exploit is weaponized, allowing for customizable payloads and automated exploitation via the Metasploit framework. The main attack vector is through a browser visiting the attacker's server, which triggers the Java applet and exploits the vulnerability to execute arbitrary code on the client. The only fingerprintable endpoint is the malicious JAR file served by the module.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.