dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21023

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

An unauthenticated attacker can exploit the LOV (List of Values) component in Oracle E-Business Suite versions 12.2.3-12.2.13 via HTTP parameter tampering. The vulnerability requires human interaction and allows unauthorized read, insert, update, and delete access to a subset of application data. The scope change indicates the attack can impact additional products beyond the directly affected component.

MitigationApply Oracle's Critical Patch Update (CPU) for April 2024 or later, which includes the fix for CVE-2024-21023. Verify the patch has been applied to all Oracle E-Business Suite instances in the environment.

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 is running
    Access the Oracle E-Business Suite login page (typically at /OA_HTML/AppsLogin) or check running application processes. Use 'ps -ef | grep applmgr' on application servers to identify E-Business Suite processes.
    Affected if Oracle E-Business Suite is running and accessible via HTTP/HTTPS
  2. Identify Oracle Complex Maintenance Repair And Overhaul version
    Navigate to the Complex Maintenance Repair And Overhaul module (typically under Service > Depot Repair) or query the Oracle Applications version using 'adident Header $APPL_TOP/xx/in/xx/invdppb.pc' where xx/in is the module's top directory. Alternatively, check the version from Oracle Applications Manager.
    Affected if The installed version is >= 12.2.3 and <= 12.2.13
  3. Verify if LOV component is accessible
    Attempt to access the List of Values (LOV) popup windows within the Complex Maintenance Repair And Overhaul module. Try navigating to a page with an LOV field (such as a search or query page) and inspect if the LOV button triggers an HTTP request to /OA_HTML/lov.jsp or similar LOV endpoints.
    Affected if LOV functionality is enabled and accessible without authentication restrictions
  4. Check if April 2024 CPU patch has been applied
    Query the Oracle patch inventory using 'adpatch' or 'opatch lsinventory' commands on the application tier. Look for patches corresponding to Oracle Critical Patch Update April 2024 (likely containing CVE-2024-21023 fixes). In Oracle Applications Manager, check the 'Applied Patches' section.
    Affected if The April 2024 Critical Patch Update has NOT been applied to the environment

If Oracle E-Business Suite with Complex Maintenance Repair And Overhaul versions 12.2.3-12.2.13 is running, the LOV component is exposed, and the April 2024 CPU patch has not been applied, the environment is vulnerable to CVE-2024-21023.

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's Critical Patch Update (CPU) for April 2024 or later, which includes the fix for CVE-2024-21023. Verify the patch has been applied to all Oracle E-Business Suite instances in the environment.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later PSU containing CVE-2024-21023 fix

  1. Check Oracle Critical Patch Update (CPU) advisories for April 2024 or later for CVE-2024-21023
  2. Apply the relevant security patch for Oracle E-Business Suite 12.2.x from My Oracle Support (MOS)
  3. Alternatively, upgrade to a later Oracle E-Business Suite 12.2.x patch set update (PSU) that includes the fix
  4. Verify the patch was applied successfully by checking the Oracle application version
Caveat Review Oracle E-Business Suite 12.2.14 release notes for any functional changes before upgrading

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
  • 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-21023 — 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-21023 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