CVE-2009-3867 is a stack-based buffer overflow in the HsbParser.getSoundBank function in Sun Java SE. According to the provided content, 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. The vulnerability can be triggered via a long file: URL supplied in an argument, leading to memory corruption on the stack. The flaw is identified as Sun Bug Id 6854303. The provided description states that remote attackers may exploit this condition to execute arbitrary code.
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 (2 hidden).
This repository contains a single Metasploit module: 'java_getsoundbank_bof.rb', which exploits a buffer overflow vulnerability (CVE-2009-3867) in the getSoundbank function of the Sun Java JRE. The exploit is weaponized and acts as a malicious HTTP server, serving a crafted Java applet (CVE-2009-3867.jar) to victims who visit the attacker's web page. The module supports multiple platforms (Windows and Mac OS X) and architectures (x86, PPC), and allows the attacker to deliver a native payload (such as a reverse shell) to the victim. The exploit targets users running vulnerable versions of Sun Java JRE with browser plugin enabled. The structure is typical for a Metasploit browser exploit: it includes HTTP server logic, target selection based on User-Agent, and dynamic payload delivery via a Java applet. The only fingerprintable endpoint is the malicious JAR file served to the victim. The module is operational and can be used to achieve remote code execution on affected systems.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.