dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21026

HIGH · 7.1 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to after 12.2.13 or later.
See remediation →
78/100
Remediation priority · High
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 the List of Values (LOV) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module (versions 12.2.3-12.2.13). Allows unauthenticated remote attackers to gain limited unauthorized read and write access to some application data through the LOV functionality, requiring human interaction (e.g., tricking a user into clicking a malicious link). The scope change indicates the attack may impact additional Oracle products beyond the primary target.

MitigationApply the relevant Oracle Critical Patch Update for Oracle E-Business Suite. Since human interaction is required for exploitation, implementing URL filtering and user awareness training on malicious link risks provides supplemental defense-in-depth.

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
Low

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

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 if Oracle E-Business Suite is installed
    Review your system inventory or consult Oracle Application Express/Oracle E-Business Suite documentation to confirm the presence of Oracle E-Business Suite in your environment.
    Affected if Oracle E-Business Suite is not present in the environment, then this CVE does not apply.
  2. Determine the installed Oracle E-Business Suite version
    Access the Oracle E-Business Suite administrator console or use the standard Oracle version query interface to retrieve the current installed version number.
    Affected if The installed version falls within the range 12.2.3 through 12.2.13, the environment is potentially affected.
  3. Verify if the Complex Maintenance, Repair, and Overhaul (CVMRO) module is enabled
    Check the Oracle E-Business Suite module configuration or responsibility assignments to determine whether the CVMRO module is active or assigned to any responsibilities.
    Affected if The CVMRO module is enabled or accessible to users, the vulnerable LOV component may be present.
  4. Confirm external HTTP accessibility of the LOV functionality
    Review Oracle E-Business Suite web listener configuration (Oracle HTTP Server or Oracle Web Listener settings) to determine if the CVMRO LOV endpoints are exposed to unauthenticated HTTP access.
    Affected if The LOV functionality is accessible via unauthenticated HTTP requests from external networks, the vulnerability is exploitable.

The environment is affected if Oracle E-Business Suite version 12.2.3 through 12.2.13 is installed, the CVMRO module is enabled, and the LOV component is accessible via unauthenticated HTTP connections.

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 relevant Oracle Critical Patch Update for Oracle E-Business Suite. Since human interaction is required for exploitation, implementing URL filtering and user awareness training on malicious link risks provides supplemental defense-in-depth.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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