dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21033

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 HTTP vulnerability in the List of Values (LOV) component of Oracle Complex Maintenance, Repair, and Overhaul (E-Business Suite versions 12.2.3-12.2.13) allows remote attackers to perform unauthorized read and write operations on data via the LOV module without credentials, but requires human interaction to execute the attack.

MitigationApply Oracle Critical Patch Update for CVE-2024-21033 to Oracle E-Business Suite 12.2.3-12.2.13, or implement network-level access controls to restrict HTTP access to trusted users only.

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 version
    Run the command 'select release_name from fnd_product_groups' in the APPS schema, or check the 'AD_SESSIONS' or 'FND_PRODUCT_RELEASES' tables to determine the installed E-Business Suite version.
    Affected if The version returned is 12.2.3 through 12.2.13 inclusive.
  2. Confirm Complex Maintenance Repair and Overhaul is installed
    Query the 'FND_PRODUCT_RELEASES' table for rows where product_name contains 'Complex Maintenance' or check for the presence of the CMRO/RMA application tier.
    Affected if The CMRO (Complex Maintenance, Repair, and Overhaul) module is present on the system.
  3. Locate the LOV module endpoint
    Search web server configuration files (like Oracle HTTP Server.conf) for paths containing '/LOV/' or 'ListOfValues', and review the application context XML files for LOV servlet mappings.
    Affected if The LOV servlet is mapped and accessible via HTTP listener.
  4. Verify HTTP accessibility of LOV endpoint
    Attempt a HEAD or GET request to the LOV endpoint (typically /OA_HTML/LOV or /forms/LOV) from an untrusted network location, or review access logs for unauthenticated HTTP requests to LOV paths.
    Affected if The LOV module responds to HTTP requests without requiring Oracle Application authentication.
  5. Check for presence of CVE-2024-21033 patch
    Query Oracle OPatch (opatch lspatches) or review the applied patches list for CPUJAN2024 or later Critical Patch Update containing CVE-2024-21033.
    Affected if The patch for CVE-2024-21033 is NOT applied and the version falls within 12.2.3-12.2.13.

You are affected if Oracle E-Business Suite version is between 12.2.3 and 12.2.13, the CMRO module is installed, and the LOV component is accessible over HTTP without authentication.

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 Critical Patch Update for CVE-2024-21033 to Oracle E-Business Suite 12.2.3-12.2.13, or implement network-level access controls to restrict HTTP access to trusted users only.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later (via quarterly Critical Patch Update)

  1. 1. Subscribe to Oracle Critical Patch Updates to receive security patches: https://www.oracle.com/security-alerts/
  2. 2. Apply the April 2024 Critical Patch Update (CPU) or later, which addresses CVE-2024-21033
  3. 3. Verify the patch was applied successfully by checking the Oracle application version and confirming the security fix is included
  4. 4. Test the LOV (List of Values) component functionality in the Oracle Complex Maintenance, Repair, and Overhaul module to ensure normal operation
Caveat Standard Oracle CPU patch application carries minimal risk but should be tested in a non-production environment first; review Oracle CPU pre-install requirements

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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