dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21039

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

Oracle E-Business Suite Complex Maintenance, Repair, and Overhaul contains an unauthenticated vulnerability in the List of Values (LOV) component. Attackers with network access via HTTP can exploit this flaw, which requires human interaction, to achieve unauthorized read and write access to a subset of accessible data. The vulnerability affects versions 12.2.3 through 12.2.13 and involves a scope change where attacks may impact additional products.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21039 to the affected Oracle E-Business Suite installation. Prior to production deployment, test the patch in a non-production environment to verify compatibility with existing customizations.

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 installation
    Locate the E-Business Suite installation directory or check for Oracle application server processes (such as Oracle HTTP Server or Oracle Application Server). Look for the presence of the E-Business Suite middleware home and application tier.
    Affected if Oracle E-Business Suite is installed and running
  2. Verify CMRO module is configured
    Check if the Complex Maintenance, Repair, and Overhaul (CMRO) module is installed and enabled within the Oracle E-Business Suite. This can be done by querying the Oracle Applications tables (such as FND_PRODUCT_INSTALLATIONS) or checking the module availability in the Oracle Applications Manager.
    Affected if The CMRO module is installed and registered in the E-Business Suite
  3. Check E-Business Suite version against affected range
    Determine the installed E-Business Suite version. This can be obtained from the Oracle Applications Manager, by querying the FND_PRODUCT_GROUPS table, or by checking the version file in the APPL_TOP directory. Confirm the version falls between 12.2.3 and 12.2.13 inclusive.
    Affected if The installed version is 12.2.3, 12.2.4, 12.2.5, 12.2.6, 12.2.7, 12.2.8, 12.2.9, 12.2.10, 12.2.11, 12.2.12, or 12.2.13
  4. Verify HTTP accessibility of the LOV component
    Check if the Oracle E-Business Suite web interfaces (particularly the LOV functionality within CMRO) are accessible over HTTP/HTTPS from the network. This vulnerability is exploited via HTTP requests to the LOV component.
    Affected if The E-Business Suite web interfaces are accessible externally or on untrusted networks

You are affected if Oracle E-Business Suite with the CMRO module is installed, the version is between 12.2.3 and 12.2.13, and the LOV component is accessible via HTTP from a network where attackers can send requests requiring human interaction.

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.

From vendor data
Upgrade available Upgrade to a release after 12.2.13
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21039 to the affected Oracle E-Business Suite installation. Prior to production deployment, test the patch in a non-production environment to verify compatibility with existing customizations.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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