Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-21034 Overview
CVE-2024-21034 affects the Oracle Complex Maintenance, Repair, and Overhaul (cMRO) product within Oracle E-Business Suite. The flaw resides in the List of Values (LOV) component across supported versions 12.2.3 through 12.2.13. An unauthenticated attacker with network access via HTTP can exploit the issue when a legitimate user interacts with attacker-supplied content. Successful exploitation produces a scope change, affecting resources beyond the vulnerable component. Attackers can gain unauthorized read access to a subset of cMRO data and perform unauthorized update, insert, or delete operations against some accessible data.
Critical Impact
Remote attackers can manipulate cMRO data integrity and read restricted information by convincing an authenticated user to interact with crafted HTTP content, with impacts crossing into additional Oracle E-Business Suite components.
Affected Products
- Oracle Complex Maintenance, Repair, and Overhaul version 12.2.3
- Oracle Complex Maintenance, Repair, and Overhaul versions 12.2.4 through 12.2.12
- Oracle Complex Maintenance, Repair, and Overhaul version 12.2.13
Discovery Timeline
- 2024-04-16 - Oracle publishes advisory in Critical Patch Update April 2024 and CVE-2024-21034 published to NVD
- 2026-06-17 - Last updated in NVD database
Technical Details for CVE-2024-21034
Vulnerability Analysis
The vulnerability resides in the LOV (List of Values) component of Oracle cMRO, part of Oracle E-Business Suite. The CVSS vector indicates that exploitation requires user interaction and causes a scope change, meaning the vulnerable component affects resources it does not directly own. This behavior is consistent with a client-side injection class of flaw, where attacker-controlled input renders inside a trusted browsing context used by E-Business Suite users. The resulting impact includes limited unauthorized data modification and limited unauthorized data disclosure within cMRO-accessible data sets. Oracle categorized the weakness under [CWE-269] (Improper Privilege Management) alongside an unspecified NVD classification.
Root Cause
The root cause is improper handling of input processed by the LOV component in cMRO. Because the component is reachable over HTTP without authentication and user interaction propagates attacker-controlled data into a trusted session context, the LOV surface fails to enforce boundaries between untrusted input and privileged E-Business Suite functionality. The scope-change characteristic indicates that the authorization context of the interacting user is leveraged to perform actions outside the LOV component itself.
Attack Vector
An unauthenticated remote attacker crafts an HTTP request or link targeting the LOV endpoint in a vulnerable Oracle cMRO deployment. The attacker then induces a legitimate authenticated E-Business Suite user to interact with the crafted content. Upon interaction, the attacker is able to read a subset of cMRO data and perform unauthorized update, insert, or delete operations against some cMRO-accessible data, with effects extending to additional Oracle E-Business Suite products.
No verified public proof-of-concept code is available for this vulnerability. Refer to the Oracle Critical Patch Update April 2024 advisory for additional technical context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2024-21034
Indicators of Compromise
- Unexpected HTTP requests targeting cMRO LOV endpoints originating from external or untrusted networks.
- Unexplained create, update, or delete operations on cMRO records that do not correlate with authorized maintenance workflows.
- E-Business Suite audit log entries showing session activity from authenticated users immediately after inbound links or email interactions.
Detection Strategies
- Monitor HTTP traffic to Oracle E-Business Suite application servers for anomalous query parameters or encoded payloads directed at LOV servlets.
- Correlate web access logs with database-level audit trails on cMRO tables to identify data changes without a corresponding business process.
- Alert on HTTP referrers pointing to external domains preceding sensitive cMRO transactions.
Monitoring Recommendations
- Enable Oracle E-Business Suite framework and FND (Foundation) audit logging for the cMRO module and forward logs to a centralized SIEM.
- Baseline normal LOV request patterns per user role and alert on deviations in request volume or structure.
- Review Oracle HTTP Server access logs for suspicious user-agent strings and parameter tampering targeting cMRO URIs.
How to Mitigate CVE-2024-21034
Immediate Actions Required
- Apply the April 2024 Oracle Critical Patch Update to all affected Oracle E-Business Suite 12.2.x environments running Oracle cMRO.
- Restrict external HTTP exposure of Oracle E-Business Suite endpoints and place the application behind authenticated reverse proxies or VPN access where feasible.
- Educate cMRO users to avoid clicking unsolicited links purporting to originate from internal maintenance systems.
Patch Information
Oracle addressed CVE-2024-21034 in the Critical Patch Update released on April 16, 2024. Administrators should consult the Oracle Critical Patch Update April 2024 advisory for the specific patch identifiers applicable to each supported release of Oracle E-Business Suite 12.2 and apply them per Oracle's recommended patching procedures.
Workarounds
- Limit network reachability of the cMRO LOV component to internal, trusted network segments until patching is complete.
- Deploy web application firewall rules to inspect and filter requests to cMRO LOV endpoints for suspicious parameters.
- Where business processes allow, temporarily disable or restrict cMRO user roles that have broad data modification privileges.
# Configuration example
# Example WAF rule concept to filter requests to cMRO LOV endpoints
# (adapt syntax to your specific WAF platform)
SecRule REQUEST_URI "@contains /OA_HTML/" \
"id:1002101,\
phase:2,\
deny,\
status:403,\
msg:'Suspicious parameter in Oracle cMRO LOV request',\
chain"
SecRule ARGS "@rx (?i)(<script|javascript:|onerror=)" \
"t:none,t:urlDecodeUni"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

