dbcve.org
Complex Maintenance Repair And OverhaulApplication · Oracle

CVE-2024-21046

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 LOV (List of Values) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module. Allows unauthenticated remote attackers to read and modify a subset of accessible data via HTTP, but requires victim user interaction (e.g., clicking a crafted link). The scope change indicates potential impact to other Oracle products.

MitigationApply the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21046. Until the patch is available, restrict network access to Oracle E-Business Suite HTTP interfaces and monitor for suspicious LOV queries.

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 installation
    Locate Oracle EBS directories (commonly under $ORACLE_HOME or in IIS/Oracle HTTP Server docroot), or check for Oracle HTTP Server (OHS) listeners running on ports like 8000, 7777, or 4444
    Affected if Oracle E-Business Suite is present and running
  2. Determine Complex Maintenance Repair And Overhaul module version
    Query the module version through Oracle EBS Administration UI, or check version files in the $OA_HTML directory, or run SQL query SELECT version FROM apps.fnd_product_groups WHERE product_group_name LIKE '%CMRO%'
    Affected if Version is 12.2.3 through 12.2.13 inclusive
  3. Confirm LOV component is HTTP-accessible
    Attempt to access the LOV endpoint (typically /OA_HTML/xxlov.jsp or similar /lov/ paths under the EBS web tier) via HTTP GET request
    Affected if LOV component responds to HTTP requests without authentication
  4. Verify HTTP interface network exposure
    Review firewall rules, load balancer configurations, and EBS web tier access control lists to determine if the LOV endpoint is reachable from untrusted networks
    Affected if HTTP interface is exposed to the internet or untrusted internal networks without IP/restriction filtering
  5. Inspect HTTP access logs for suspicious LOV queries
    Review Oracle HTTP Server access logs (in $ORACLE_HOME/Apache/logs or equivalent) and EBS application logs for anomalous LOV parameter patterns, especially with user interaction indicators
    Affected if Unusual or crafted LOV query strings appear in logs, particularly from unauthenticated sources

The environment is affected if Oracle EBS with Complex Maintenance Repair And Overhaul version 12.2.3-12.2.13 is running with the LOV component accessible via HTTP from an untrusted network.

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 the Oracle Critical Patch Update (CPU) that addresses CVE-2024-21046. Until the patch is available, restrict network access to Oracle E-Business Suite HTTP interfaces and monitor for suspicious LOV queries.

Recommended fix High confidence

Oracle Complex Maintenance, Repair, and Overhaul 12.2.14 or later (or apply April 2024 CPU)

  1. Identify the current Oracle E-Business Suite installation version by checking the Oracle Applications Manager (OAM) or running adident utilities
  2. Confirm the exact 12.2.x version currently deployed in the environment
  3. Download and review the Oracle Critical Patch Update (CPU) advisory for April 2024 which addresses CVE-2024-21046
  4. Apply the April 2024 CPU patchset, or upgrade to Oracle Complex Maintenance, Repair, and Overhaul version 12.2.14 or later
  5. After applying the patch or upgrade, verify the fix by confirming the LOV component no longer reflects unescaped user input in the List of Values screens
  6. Test the fix in a non-production environment before deploying to production
  7. Deploy the fix to production environment following standard Oracle E-Business Suite change management procedures
Caveat Standard Oracle E-Business Suite upgrade considerations apply - test custom integrations and ensure third-party integrations are compatible with the target version

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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