dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21017

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 attacker can exploit a vulnerability in the LOV (List of Values) component of Oracle Complex Maintenance, Repair, and Overhaul to achieve unauthorized read and write access to some data. The attack requires human interaction and can impact additional products due to scope change. The CVSS vector indicates a classic IDOR or broken access control issue exploitable over the network without credentials.

MitigationApply the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21017 to Oracle E-Business Suite versions 12.2.3-12.2.13. Prior to production deployment, test thoroughly in a non-production environment given the scope change potential.

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 CMRO/EBS version
    Log into Oracle Application Manager (OAM) or navigate to the Oracle E-Business Suite home page. The version is typically displayed in the banner or can be retrieved by querying the FND_PRODUCT_GROUPS table: SELECT product_version FROM fnd_product_groups WHERE product = 'CMRO';
    Affected if The installed version is between 12.2.3 and 12.2.13 inclusive (12.2.x)
  2. Confirm LOV component is present
    The LOV (List of Values) is a standard Oracle Forms feature. Access any form in the Complex Maintenance, Repair, and Overhaul module that contains a lov button (magnifying glass icon). If the lov functionality is present and functional, the component exists.
    Affected if The LOV component is available and accessible within the CMRO module forms
  3. Verify LOV functionality is enabled
    Check Oracle Forms configuration files (formsweb.cfg) to ensure the lov plugin or functionality is not explicitly disabled. Also verify that Forms server is running and responding.
    Affected if LOV functionality is enabled and the Forms server is operational (this is the default state)
  4. Assess network exposure
    Determine if the Oracle E-Business Suite web interfaces (OA_HTML/OA.jsp for CMRO) are accessible from the network. Check the URL endpoints accessible: /OA_HTML/LC.* and verify which hosts can reach them.
    Affected if The CMRO/LOV endpoints are reachable over the network from untrusted locations without authentication

You are affected if your Oracle CMRO/EBS version is 12.2.3 through 12.2.13 and the LOV component is accessible, since this IDOR vulnerability requires no authentication to exploit.

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 (CPU) for CVE-2024-21017 to Oracle E-Business Suite versions 12.2.3-12.2.13. Prior to production deployment, test thoroughly in a non-production environment given the scope change potential.

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-21017 — 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-21017 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