dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21032

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

This is an access control vulnerability in the LOV (List of Values) component of Oracle Complex Maintenance, Repair, and Overhaul module in Oracle E-Business Suite. The flaw allows unauthenticated remote attackers via HTTP to perform unauthorized read and write operations on a subset of MRO data, requiring user interaction (likely a click or social engineering) to trigger the attack. The scope change indicates the vulnerability can impact other connected products.

MitigationApply Oracle's Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21032. Since this is an EBS module patch, follow Oracle's standard patching process with thorough testing in a non-production environment before production deployment.

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 deployed
    Identify if Oracle EBS is running in your environment by checking for Oracle application servers, EBS web tier processes, or by querying your inventory/CMDB for Oracle E-Business Suite installations
    Affected if Oracle EBS is not present in the environment, the vulnerability does not apply
  2. Verify the MRO module is installed
    Check if the Complex Maintenance, Repair, and Overhaul (MRO) module is enabled in your Oracle EBS instance. This can be done via Oracle Application Manager (OAM) or by querying the Oracle EBS registered applications tables
    Affected if The MRO module is not installed or not enabled, the vulnerability does not apply
  3. Determine the installed MRO version
    Locate the version of the Oracle Complex Maintenance Repair And Overhaul module installed. In Oracle EBS, this is typically accessible through the Oracle Application Manager > Oracle Applications > About Oracle Applications page, or via the adlicinsh.sql utility. Compare the version number against the affected range 12.2.3 through 12.2.13
    Affected if The MRO version falls outside 12.2.3 to 12.2.13 (either below 12.2.3 or above 12.2.13), the vulnerability does not apply
  4. Check if HTTP access to LOV component is enabled
    Examine the Oracle EBS web listener configuration to determine if the LOV (List of Values) component for the MRO module is accessible via HTTP. This typically involves checking the Oracle HTTP Server (OHS) or Apache configuration for the MRO application endpoints
    Affected if The LOV component is not exposed via HTTP (only internal or disabled), the attack vector is not available

Your environment is affected by CVE-2024-21032 if you have Oracle E-Business Suite with the MRO module enabled, running version 12.2.3 through 12.2.13, and the MRO LOV component is accessible via HTTP.

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 that addresses CVE-2024-21032. Since this is an EBS module patch, follow Oracle's standard patching process with thorough testing in a non-production environment before production deployment.

Recommended fix Low confidence

Oracle E-Business Suite 12.2.14 or later (or apply the relevant Critical Patch Update containing the fix for CVE-2024-21032)

  1. 1. Review the Oracle E-Business Suite Critical Patch Update (CPU) program and apply the latest CPU that addresses CVE-2024-21032.
  2. 2. Download the required security patches from Oracle Support using your Oracle Support credentials.
  3. 3. Before applying patches to production, test the CPU in a staging or development environment.
  4. 4. Apply the CPU following Oracle's standard EBS patch application procedures (using adop or similar tools).
  5. 5. Validate that the CSRF protection is functioning correctly after the patch is applied.
  6. 6. Review Oracle's patch deployment documentation and ensure all post-installation steps are completed.
Caveat Standard Oracle CPU apply risks apply - test thoroughly in non-production first; some CPU patches may require additional post-install steps or have compatibility considerations

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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing12.0 h
  • Review / QA6.0 h
36.0 hours of engineering $6,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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