dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21036

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-based vulnerability in the LOV (List of Values) component of Oracle Complex Maintenance, Repair, and Overhaul (CMRO) versions 12.2.3-12.2.13. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) combined with the impact description (unauthorized read/update/insert/delete access) and requirement for human interaction strongly suggests a reflected injection flaw (likely XSS or HTML injection) in the LOV web interface. The scope change indicates attacks can impact additional Oracle E-Business Suite products beyond CMRO.

MitigationApply Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21036 to Oracle E-Business Suite 12.2.3-12.2.13. Until patches are applied, consider restricting HTTP access to CMRO to trusted networks and implement web application firewall rules for the LOV endpoint.

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 CMRO is installed
    Access Oracle Applications Manager or check the Oracle E-Business Suite system for the presence of the Complex Maintenance, Repair, and Overhaul module. Look for CMRO-specific web directories or application paths in the Oracle Application Server.
    Affected if CMRO module is not present in the Oracle E-Business Suite installation (not applicable)
  2. Verify CMRO version
    Locate the installed CMRO version through Oracle Applications Manager, the Oracle E-Business Suite version information screen, or by querying the Oracle database for the CMRO release version. Common paths include the About CMRO page or the Applications Dashboard.
    Affected if Installed version falls within 12.2.3 through 12.2.13 inclusive (vulnerable range)
  3. Identify LOV component exposure
    Attempt to access the LOV (List of Values) web interface for CMRO. This is typically found under the OA_HTML directory or similar Oracle Application Framework paths used by CMRO for LOV popups. Check if the LOV endpoint responds to HTTP requests.
    Affected if The CMRO LOV component is accessible via HTTP and responds to requests (endpoint exists and is reachable)
  4. Assess network accessibility
    Determine if the CMRO web interface (including the LOV component) is accessible from untrusted networks. Check firewall rules, load balancer configurations, and web server access controls that govern exposure of the CMRO application URLs.
    Affected if The CMRO LOV endpoint is accessible from untrusted networks (network-facing)

The environment is affected if Oracle CMRO version 12.2.3-12.2.13 is installed and the LOV web component is network-accessible, allowing unauthenticated HTTP requests to reach the vulnerable endpoint.

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 Oracle Critical Patch Update (CPU) containing the fix for CVE-2024-21036 to Oracle E-Business Suite 12.2.3-12.2.13. Until patches are applied, consider restricting HTTP access to CMRO to trusted networks and implement web application firewall rules for the LOV endpoint.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later

  1. Check the current Oracle E-Business Suite version by navigating to the About Oracle Applications page
  2. Review Oracle's Critical Patch Update advisory for April 2024 (or subsequent CPU) to obtain the security fix for CVE-2024-21036
  3. Apply the relevant security patch from the Oracle Critical Patch Update, or upgrade to version 12.2.14 or higher
  4. After applying the patch or upgrade, verify the fix by testing the LOV (List of Values) component for proper input validation
  5. Confirm the version has been updated by checking the system administration console
Caveat Review Oracle's upgrade documentation for E-Business Suite 12.2.14 for any functional changes or deprecated features before production deployment

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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