dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21040

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 vulnerability in the LOV (List of Values) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module. Exploitable via HTTP without credentials but requires human interaction (likely social engineering to trick a valid user). Allows unauthorized read, insert, update, and delete access to data. The scope change indicates attacks may impact additional products beyond the primary component.

MitigationApply Oracle Critical Patch Update (CPU) for April 2024 that addresses this vulnerability. Until patches are applied, restrict network access to affected EBS instances and consider deploying a WAF 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. Verify Oracle E-Business Suite installation
    Check for the presence of Oracle E-Business Suite by reviewing installed applications or checking for EBS-related processes, services, or web directories on the server.
    Affected if Oracle E-Business Suite is not installed - the CVE does not apply.
  2. Check Complex Maintenance Repair And Overhaul module version
    Access the Oracle Applications Manager (OAM) or use the adident utility (adident Header $AF_TOP/filename) to determine the version of the CMRO module. Alternatively, query the Oracle database: SELECT release_name FROM apps.fnd_product_groups;
    Affected if The installed version is between 12.2.3 and 12.2.13 inclusive - the version is within the affected range.
  3. Confirm HTTP listener is enabled for EBS
    Check if Oracle E-Business Suite is configured to accept HTTP connections by reviewing the context file (context_name.xml) for the 's_webport' parameter or by attempting to access the EBS login page over HTTP (port 8000 typically).
    Affected if HTTP access is enabled and the EBS instance is reachable via HTTP - the vulnerability is exploitable over this protocol.
  4. Assess network exposure of the EBS web interface
    Review firewall rules, load balancer configurations, or network ACLs to determine if the EBS HTTP port (typically 8000, 8080, or 443) is accessible from untrusted networks or the internet.
    Affected if The EBS HTTP interface is exposed to untrusted networks or the internet - unauthenticated attackers can reach the vulnerable endpoint.
  5. Check for presence of LOV component endpoint
    Review the Oracle EBS web configuration files (like apps.conf or oracle_apache.conf) for the LOV-related module paths under the CMRO application. Attempt a HEAD request to typical LOV endpoints if accessible.
    Affected if The LOV component for CMRO is accessible via the web listener - this is the specific attack surface for this CVE.

The environment is affected if Oracle E-Business Suite with Complex Maintenance Repair And Overhaul version 12.2.3 through 12.2.13 is exposed via HTTP to untrusted networks, allowing unauthenticated attackers to exploit the LOV component.

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 Oracle Critical Patch Update (CPU) for April 2024 that addresses this vulnerability. Until patches are applied, restrict network access to affected EBS instances and consider deploying a WAF to filter malicious requests.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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