CVE-2010-4417

CVE-2010-4417 is a high-severity vulnerability in Oracle Beehive with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 79% places it in the 100th percentile, indicating an elevated likelihood of exploitation.

Key facts

Description

Unspecified vulnerability in the Services for Beehive component in Oracle Fusion Middleware 2.0.1.0, 2.0.1.1, 2.0.1.2, 2.0.1.2.1, and 2.0.1.3 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the January 2011 CPU. Oracle has not commented on claims from a reliable third party coordinator that voice-servlet/prompt-qa/Index.jspf does not properly handle null (%00) bytes in the evaluation parameter that is used in a filename, which allows attackers to create a file with an executable extension and execute arbitrary JSP code.

Frequently asked questions

What is CVE-2010-4417?
Unspecified vulnerability in the Services for Beehive component in Oracle Fusion Middleware 2.0.1.0, 2.0.1.1, 2.0.1.2, 2.0.1.2.1, and 2.0.1.3 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors. NOTE: the previous information was obtained from the January 2011 CPU. Oracle has not commented on claims from a reliable third party coordinator that voice-servlet/prompt-qa/Index.jspf does not properly handle null (%00) bytes in the evaluation parameter that is used in a filename, which allows attackers to create a file with an executable extension and execute arbitrary JSP code.
How severe is CVE-2010-4417?
CVE-2010-4417 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2010-4417 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 79% (100th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2010-4417?
CVE-2010-4417 primarily affects Oracle Beehive. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2010-4417?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2010-4417 published?
CVE-2010-4417 was published on 2011-01-19 and last updated on 2026-06-16.

References

Affected products (5)