dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21028

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 allows attackers to gain unauthorized read and write access to a subset of data through network requests, requiring human interaction to exploit.

MitigationApply Oracle Critical Patch Update when available; until then, restrict network access to the affected E-Business Suite endpoints and consider deploying a WAF to detect and block exploitation attempts.

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 if Oracle E-Business Suite CMRO is installed
    Check for Oracle E-Business Suite processes running, or query the Oracle applications registry for the Complex Maintenance Repair And Overhaul module using SQL: SELECT product_version, status FROM apps.fnd_product_installations WHERE product = 'CSD' OR product LIKE '%Maintenance%';
    Affected if The CMRO module is not found or not installed, then this CVE does not apply.
  2. Determine the installed CMRO version
    Query the Oracle E-Business Suite version tables: SELECT release_name FROM apps.fnd_product_groups; or check the CSD_VERSION in fnd_application for the maintenance module.
    Affected if The version falls within the range >= 12.2.3 and <= 12.2.13, meaning the system is potentially affected.
  3. Verify the HTTP/List of Values interface is accessible
    Check the Oracle E-Business Suite Apache/OHS configuration files (httpd.conf, apps.conf) for the /LOV/ or /OA_HTML/ path mappings, and attempt a GET request to a known LOV endpoint such as /OA_HTML/LOV or test connectivity to port 80/443.
    Affected if The HTTP interface for the LOV component is exposed and responds to requests, making network-based exploitation possible.
  4. Assess network accessibility of the affected endpoints
    Review firewall rules, load balancer access control lists, or WebGate configuration to determine if the E-Business Suite /LOV/ paths are reachable from untrusted networks without authentication.
    Affected if The endpoints are accessible from outside the trusted network without proper authentication controls, indicating vulnerability to unauthenticated exploitation.

If Oracle CMRO version is between 12.2.3 and 12.2.13 and the HTTP LOV component is network-accessible without authentication, the environment is affected by this CVE.

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 Oracle Critical Patch Update when available; until then, restrict network access to the affected E-Business Suite endpoints and consider deploying a WAF to detect and block exploitation attempts.

Fix this in Complex Maintenance Repair And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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