dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21035

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 · moderate confidence

Unauthenticated HTTP vulnerability in the LOV (List of Values) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module (versions 12.2.3-12.2.13). Attackers can achieve unauthorized read, insert, update, or delete access to a subset of data through the LOV component. Exploitation requires human interaction (social engineering to click a malicious link) and may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Update for CVE-2024-21035; meanwhile, restrict HTTP access to the affected Oracle EBS endpoints via network segmentation or WAF rules to reduce exposure.

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. Verify Oracle EBS version in affected range
    Query the Oracle Applications version: SELECT release_name FROM apps.fnd_product_groups; or check the $APPL_TOP/../comn/validrep/oracle*version*.txt file
    Affected if Installed version is 12.2.3 through 12.2.13 inclusive
  2. Confirm Complex Maintenance, Repair and Overhaul (CMRO) module is installed
    Query: SELECT application_name, status FROM dba_segments WHERE segment_name LIKE '%CMRO%'; or check in Oracle Applications Manager (OAM) -> Security -> Module History
    Affected if CMRO module status shows as INSTALLED or ENABLED
  3. Identify if HTTP listeners are exposed for the LOV component
    Review web server configuration files (httpd.conf, context.xml) or check Oracle EBS URL patterns: /webservices/LOV/* or /OA_HTML/LOV/* paths are accessible
    Affected if HTTP port 8000/8001 or web URLs for the EBS instance are externally accessible without restriction
  4. Review Oracle EBS access logs for suspicious LOV parameter patterns
    Examine access logs in $LOG_HOME/ora/10.1.3/Apache or equivalent for requests with unusual LOV queries, especially with INSERT/UPDATE/DELETE operations
    Affected if LOV-related requests contain unexpected SQL operations or originate from untrusted sources
  5. Check for unauthorized data modifications in CMRO tables
    Query CMRO-related tables (INV.MTL_SYSTEM_ITEMS, or custom CMRO tables) for unexpected records or changes: SELECT * FROM <cmro_table> WHERE created_by NOT IN (SELECT user_id FROM fnd_user);
    Affected if Records exist that were created or modified by unexpected users or outside normal business hours

A user is affected if they run Oracle EBS version 12.2.3-12.2.13 with the CMRO module installed and the LOV component is accessible via HTTP, regardless of whether exploitation has occurred.

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-21035; meanwhile, restrict HTTP access to the affected Oracle EBS endpoints via network segmentation or WAF rules to reduce exposure.

Recommended fix Moderate confidence

Oracle E-Business Suite 12.2.14 or later (or apply April 2024 CPU)

  1. Verify current Oracle E-Business Suite version by navigating to Oracle Applications Manager > Oracle Applications Dashboard
  2. Confirm the Complex Maintenance, Repair, and Overhaul module version is 12.2.3 through 12.2.13
  3. Apply Oracle Critical Patch Update (CPU) for April 2024 or later, which addresses CVE-2024-21035
  4. Alternatively, upgrade to Oracle E-Business Suite 12.2.14 or later patch set
  5. After applying the patch/upgrade, verify the LOV component has been updated by checking the Oracle Applications Manager diagnostics
Caveat Review Oracle's April 2024 Critical Patch Update notes for any pre-requisite patches or compatibility considerations with other E-Business Suite modules

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 / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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