CVE-2024-21042
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 · uneditedVulnerability 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 confidenceUnauthenticated HTTP vulnerability in the LOV (List of Values) component of Oracle E-Business Suite's Complex Maintenance, Repair, and Overhaul module allows remote attackers to read or modify some data without credentials, but requires human interaction (e.g., tricking a user into clicking a malicious link). The scope change indicates attacks may impact additional products beyond the directly affected module.
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>= 12.2.3, <= 12.2.13CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle E-Business Suite is installedLook for Oracle E-Business Suite web tier components (Oracle HTTP Server, Oracle WebLogic Server) running or check for E-Business Suite installation directories such as $OA_HTML, $FND_TOP, or the Oracle Application Server directories.Affected if Oracle E-Business Suite web interfaces are accessible on the network
-
Identify the Complex Maintenance Repair And Overhaul (CMRO) module versionQuery the database using SQL: SELECT patch_level FROM applsys.fnd_product_installations WHERE patch_level LIKE '%CMRO%'; or check the Oracle Applications Manager (OAM) interface for the installed version of the Complex Maintenance, Repair, and Overhaul module.Affected if The installed version falls within 12.2.3 to 12.2.13 inclusive
-
Verify the LOV component is accessibleTest access to the LOV (List of Values) functionality in the CMRO module by attempting to access the typical LOV URL pattern, such as /OA_HTML/olap.jsp or checking web server access logs for requests to LOV-related servlets and JSP pages used by CMRO.Affected if The LOV component responds to HTTP requests without requiring authentication
-
Check network exposure of E-Business Suite web interfacesReview firewall rules, load balancer configurations, or Oracle WebGate/OHS configuration to determine if the E-Business Suite login pages and CMRO module are exposed to untrusted networks or the internet.Affected if The E-Business Suite web interfaces hosting CMRO are accessible from untrusted networks or the internet without proper access controls
The environment is affected if Oracle E-Business Suite with the Complex Maintenance Repair And Overhaul module version 12.2.3 through 12.2.13 is installed and its web interfaces, particularly the LOV component, are network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) for April 2024 that addresses CVE-2024-21042. Until patched, restrict network access to the E-Business Suite web interfaces and consider deploying a WAF to filter malicious requests.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-21042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-21042 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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