Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2010-4417: Arbitrary JSP Execution via Null Byte Injection in Oracle Fusion Middleware Beehive

Published Jan 19, 2011 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS76.3%100th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Oracle Corporation
IdentifiersCVE-2010-4417CWE-20

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary JSP code on the affected Oracle Fusion Middleware server, compromising confidentiality, integrity, and availability. Attackers can potentially gain full control over the application server and pivot to other internal resources.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, restrict access to the vulnerable endpoint (voice-servlet/prompt-qa/Index.jspf) via network controls or web application firewall rules. Monitor for suspicious file creation and review application logs for exploitation attempts involving null byte injection in parameters.

Remediation

Patch, then assume compromise.

Apply the relevant patches provided by Oracle in the January 2011 Critical Patch Update. Ensure all instances of Oracle Fusion Middleware are updated to a version where this vulnerability is addressed.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Oracle CorporationBeehiveapplication
FAQ

Frequently asked questions

Is CVE-2010-4417 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2010-4417 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2010-4417?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2010-4417, the earliest disclosed Jun 9, 2010.
Is there a patch for CVE-2010-4417?
Apply the relevant patches provided by Oracle in the January 2011 Critical Patch Update. Ensure all instances of Oracle Fusion Middleware are updated to a version where this vulnerability is addressed.
What products are affected by CVE-2010-4417?
Oracle Corporation Beehive.
How severe is CVE-2010-4417?
CVE-2010-4417 has a CVSS v2 score of 7.5 (High) and an EPSS score of 76.3% (100th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.