Loading vulnerability…
An uncontrolled array index vulnerability exists in the Sound component of Oracle Java SE and Java for Business (6 Update 18, 5.0 Update 23, 1.4.2_25, 1.3.1_27). The flaw allows remote attackers to execute arbitrary code by supplying a crafted MIDI file containing a malicious MixerSequencer object, exploiting improper validation of array indices in the GM_Song structure.
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/windows/browser/java_mixer_sequencer.rb) that exploits CVE-2010-0842, a vulnerability in the handling of MixerSequencer objects in Java 6u18 and earlier. The exploit works by serving a malicious web page that loads a Java applet, which in turn requests a crafted RMF file containing a specially constructed MIDI file. The MIDI file is designed to trigger a memory corruption vulnerability, allowing arbitrary code execution via a shellcode payload embedded in the file. The module sets up an HTTP server to deliver the necessary files (.jar and .rmf) to the victim. The exploit targets Windows systems running vulnerable Java versions in browsers such as Internet Explorer or Firefox. The payload is customizable and can be any Metasploit-compatible shellcode. The structure is typical for a Metasploit browser exploit: it includes methods for generating the malicious files, handling HTTP requests, and orchestrating the attack flow.
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, 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.