dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21020

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

Unauthenticated HTTP vulnerability in Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul LOV (List of Values) component allows remote attackers to inject malicious scripts or access unauthorized data through the LOV interface. The requirement for human interaction (UI:R) combined with scope change (S:C) and the C/L/I impacts without availability impact strongly suggests a reflected Cross-Site Scripting (XSS) vulnerability in the LOV query/render functionality.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21020 to the affected Oracle E-Business Suite versions 12.2.3-12.2.13. As interim measures, implement input validation on LOV parameters and consider WAF rules to filter malicious 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. Confirm Oracle E-Business Suite installation
    Locate the Oracle E-Business Suite installation directory or check for Oracle application server processes listening on standard HTTP/HTTPS ports (typically 8000-8009 for Oracle Application Server). Query the database for the current E-Business Suite version using SQL: SELECT release_name FROM apps.fnd_product_groups WHERE release_name LIKE '12.%';
    Affected if Oracle E-Business Suite is not installed or the version is outside 12.2.3-12.2.13 range
  2. Identify CMRO module configuration
    Check if the Complex Maintenance, Repair, and Overhaul (CMRO) module is installed and enabled. Query the Oracle database: SELECT application_id, application_name FROM fnd_application WHERE application_name LIKE '%Complex Maintenance%' OR application_name LIKE '%CMRO%'; Verify the module status in Oracle Applications Manager (OAM) or via ad identification utilities.
    Affected if CMRO module is not installed or not configured in the environment
  3. Verify LOV interface accessibility
    Determine if the LOV (List of Values) functionality is accessible via web. Common LOV URLs in Oracle E-Business Suite follow patterns like /OA_HTML/lov.jsp or /OA_HTML/LCID/lov/lov.jsp. Attempt to access the LOV interface for CMRO-related screens, typically under paths containing 'CMRO' or 'maint' or 'repair'.
    Affected if LOV interface is not accessible or not present in the CMRO module
  4. Test for reflected XSS in LOV parameters
    Using a web proxy or browser developer tools, submit a crafted request to the LOV endpoint with a test XSS payload in common LOV parameters such as ' lovName', 'lovId', or 'returnUrl'. Example: Append a simple test string like '<script>alert(1)</script>' to LOV query parameters and observe if the payload is reflected unescaped in the response.
    Affected if The test payload is reflected in the response without HTML encoding or the application returns the payload in the rendered LOV output

You are affected if you have Oracle E-Business Suite version 12.2.3 through 12.2.13 with the CMRO module installed and the LOV interface exposed, and the XSS test payload is reflected in LOV responses.

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 relevant Oracle Critical Patch Update (CPU) for CVE-2024-21020 to the affected Oracle E-Business Suite versions 12.2.3-12.2.13. As interim measures, implement input validation on LOV parameters and consider WAF rules to filter malicious requests.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later

  1. 1. Review Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul 12.2.x documentation for upgrade procedures
  2. 2. Download and apply Oracle E-Business Suite 12.2.14 or later version from Oracle Software Delivery Cloud
  3. 3. Test the upgrade in a non-production environment before deploying to production
  4. 4. Verify that the LOV component (List of Values) is functioning correctly after upgrade
  5. 5. Validate that CSRF protections are properly enforced in the updated version
  6. 6. Deploy the fixed version to production environment
Caveat Oracle E-Business Suite minor version upgrades may include functional changes; review release notes for any impacts to existing integrations

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21020 — 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-21020 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