dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21021

MEDIUM · 6.1 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle Complex Maintenance, Repair, and Overhaul product of Oracle E-Business Suite (component: LOV). Supported versions that are affected are 12.2.3-12.2.13. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Complex Maintenance, Repair, and Overhaul. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Complex Maintenance, Repair, and Overhaul, attacks may significantly impact additional products (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Complex Maintenance, Repair, and Overhaul accessible data as well as unauthorized read access to a subset of Oracle Complex Maintenance, Repair, and Overhaul accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an unauthenticated vulnerability in the LOV (List of Values) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) combined with the component type strongly indicates a cross-site scripting (XSS) flaw. The requirement for human interaction and the scope change (S:C) suggest the attacker must lure a legitimate user into clicking a crafted link or submitting malicious input, which then enables unauthorized read and write access to data within the affected module and potentially other connected Oracle E-Business Suite products.

MitigationApply the Oracle Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21021. Until the patch is applied, consider restricting network access to the affected E-Business Suite endpoints and implementing Web Application Firewall (WAF) rules to detect XSS attack patterns in HTTP requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Complex Maintenance Repair And OverhaulApplication
Affected:>= 12.2.3, <= 12.2.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Oracle E-Business Suite deployment
    Review your infrastructure inventory or run: sqlplus / as sysdba - execute SELECT version FROM product_component_version WHERE product LIKE 'Oracle%E-Business%'; to identify E-Business Suite installations
    Affected if Oracle E-Business Suite is not found in the environment, the system is not affected by this CVE
  2. Verify Complex Maintenance Repair And Overhaul module version
    Access the module through the E-Business Suite responsibility menu, or query: SELECT version FROM apps.fnd_product_groups WHERE product_group_name LIKE '%Complex Maintenance%'; or check the Oracle Applications Manager interface for installed versions
    Affected if The module version is >= 12.2.3 AND <= 12.2.13, placing it within the vulnerable range
  3. Confirm LOV component is accessible
    Navigate to the LOV (List of Values) function within the Complex Maintenance Repair And Overhaul module by accessing a responsibility such as 'Maintenance, Repair and Overhaul' and opening any LOV-enabled field, or examine web server access logs for requests to paths containing '/LOV/' or similar endpoints in the CMRO context
    Affected if The LOV component responds to HTTP requests, indicating it is exposed and potentially exploitable
  4. Review HTTP logs for XSS indicators
    Search web server access logs (OHS/Apache logs in $ORACLE_HOME/instance/ohs1/logs) for suspicious patterns in CMRO-related requests, such as <script>, javascript:, onerror=, onload=, or other HTML/JavaScript injection vectors in LOV parameter values
    Affected if Malicious XSS payloads are found in historical logs targeting the LOV component, indicating attempted or successful exploitation

The environment is affected if Oracle E-Business Suite with the Complex Maintenance Repair And Overhaul module is deployed AND the module version falls between 12.2.3 and 12.2.13 AND the LOV component is accessible over HTTP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21021. Until the patch is applied, consider restricting network access to the affected E-Business Suite endpoints and implementing Web Application Firewall (WAF) rules to detect XSS attack patterns in HTTP requests.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later (via Critical Patch Update)

  1. 1. Subscribe to Oracle Critical Patch Updates to receive security patches: https://www.oracle.com/security-alerts/
  2. 2. Check Oracle E-Business Suite 12.2.x Critical Patch Update advisories for CVE-2024-21021
  3. 3. Apply the relevant Oracle Critical Patch Update (CPU) that addresses this vulnerability
  4. 4. After patching, verify the fix by testing the LOV (List of Values) component for XSS vulnerability
Caveat Oracle E-Business Suite patches are cumulative; test thoroughly in a non-production environment before applying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21021 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21021 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data