dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21018

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 E-Business Suite Complex Maintenance, Repair, and Overhaul allows remote attackers with network access to read and modify a subset of accessible data without credentials, but requires human interaction (clicking a link) to initiate the attack.

MitigationApply Oracle's Critical Patch Update addressing CVE-2024-21018 to affected versions 12.2.3-12.2.13 of Oracle E-Business Suite; temporarily mitigate with WAF rules filtering suspicious LOV requests and restricting HTTP access to trusted users.

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 deployment
    Locate the E-Business Suite installation directories and confirm the application server is running Oracle EBS. Check for $EBS_HOME environment variable or standard Oracle installation paths.
    Affected if Oracle E-Business Suite is not present in the environment, the vulnerability does not apply.
  2. Verify CMRO module installation
    Check if the Complex Maintenance, Repair, and Overhaul (CMRO) module is installed. This can be done by querying the Oracle EBS database for registered modules or checking the application menu structures for CMRO-specific functions.
    Affected if The CMRO module is not installed, this specific vulnerability does not apply.
  3. Determine CMRO version number
    Access the Oracle E-Business Suite About page from the responsibility menu, or query the version information through the EBS AD Administration utilities. The version format is typically 12.2.x.
    Affected if The installed CMRO version is between 12.2.3 and 12.2.13 inclusive.
  4. Confirm HTTP access to LOV functionality
    Verify that the E-Business Suite web interfaces are accessible over HTTP/HTTPS. Test accessing the LOV functionality through the CMRO module by navigating to forms that use List of Values popup windows.
    Affected if The LOV component is accessible via HTTP without authentication, making the attack surface available.
  5. Check network exposure
    Review firewall rules and network ACLs to determine if the EBS web endpoints are exposed to untrusted networks. Identify whether the application is accessible from the internet or only from trusted internal networks.
    Affected if The EBS HTTP interfaces are reachable from untrusted network segments, allowing remote attackers to initiate the attack.

A user is affected if they have Oracle E-Business Suite with CMRO module versions 12.2.3 through 12.2.13 and the LOV component is accessible via HTTP from untrusted networks.

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 addressing CVE-2024-21018 to affected versions 12.2.3-12.2.13 of Oracle E-Business Suite; temporarily mitigate with WAF rules filtering suspicious LOV requests and restricting HTTP access to trusted users.

Recommended fix Moderate confidence
  1. Apply the latest Oracle Critical Patch Update (CPU) that includes the fix for CVE-2024-21018. Oracle CPUs are typically released quarterly (January, April, July, October).
  2. Verify with Oracle Support (My Oracle Support) that the specific patch for this vulnerability (CVE-2024-21018) is included in the CPU you are applying.
  3. Before applying any Oracle CPU patch, ensure you have a full backup of the E-Business Suite environment (database, application tier, middle tier).
  4. Test the patch in a non-production environment first to verify it resolves the vulnerability without introducing regressions.
  5. Apply the CPU patch during a scheduled maintenance window following Oracle's standard E-Business Suite patching procedures.
Caveat Applying Oracle CPU patches carries risk and may require additional regression testing; ensure thorough testing in a staging environment before production deployment

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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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