CVE-2010-4417 is a vulnerability in the Services for Beehive component of Oracle Fusion Middleware versions 2.0.1.0 through 2.0.1.3. The vulnerability is due to improper handling of null (%00) bytes in the 'evaluation' parameter of the voice-servlet/prompt-qa/Index.jspf endpoint. This allows remote attackers to create files with executable extensions, leading to arbitrary JSP code execution on the server.
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 (oracle_beehive_evaluation.rb) that exploits a remote code execution vulnerability (CVE-2010-4417) in Oracle Beehive 2's voice-servlet processEvaluation() method. The exploit works by uploading a malicious JSP stager to the target server via a crafted HTTP GET request to the /voice-servlet/prompt-qa/showRecxml.jsp endpoint. The stager allows the attacker to upload and execute a custom Windows executable (payload) on the target system with SYSTEM privileges. The module includes all necessary logic to check for the vulnerability, upload the stager, and deliver the final payload. The attack vector is network-based, targeting the Oracle Beehive HTTP service (default port 7777). The repository is structured as a typical Metasploit exploit module, written in Ruby, and leverages Metasploit's payload generation and file dropping capabilities. The exploit is weaponized, allowing for customizable payloads and automated cleanup.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.