CVE-2024-21034
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 · moderate confidenceAn unauthenticated vulnerability in the LOV (List of Values) component of Oracle Complex Maintenance, Repair, and Overhaul allows attackers with network access via HTTP to read and partially modify data without credentials. The attack requires human interaction, suggesting it may involve reflected user data or cross-site request manipulation, and scope changes indicate potential impact to integrated products.
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.
-
Identify Oracle E-Business Suite installationCheck if Oracle E-Business Suite is installed by looking for Oracle application directories (typically under $ORACLE_HOME) or by querying the database for the Oracle Applications version: SELECT release_name FROM apps.fnd_product_groups;Affected if Oracle E-Business Suite is not installed, this CVE does not apply
-
Determine Complex Maintenance, Repair, and Overhaul versionQuery the CMRO version from the database: SELECT patch_level FROM applsys.fnd_application WHERE application_id IN (SELECT application_id FROM applsys.fnd_application WHERE application_name LIKE '%Complex Maintenance%'); Or check the Oracle Applications patch level file.Affected if The version falls outside the range 12.2.3 to 12.2.13, the system is not affected by this specific CVE
-
Verify HTTP access to LOV componentCheck if the LOV (List of Values) servlet is accessible via HTTP. This typically involves checking the Oracle Application Server or Oracle WebLogic configuration for the LOV module path (commonly /OA_HTML/rlf/ or similar LOV-related servlets). Review web server configuration files and URL access logs.Affected if HTTP access to the LOV component is not enabled or the module is blocked, the exploit surface may be reduced
-
Confirm network accessibility of the affected moduleReview network segmentation and firewall rules to determine if the Oracle E-Business Suite HTTP ports (usually 8000, 8001, 443, or custom ports) are exposed to untrusted networks. Check web application firewall logs for attempts to access LOV-related endpoints.Affected if The affected LOV module is reachable from untrusted networks without authentication, the system is vulnerable to unauthenticated attacks
A system is affected if it runs Oracle Complex Maintenance, Repair, and Overhaul version 12.2.3 through 12.2.13 with the LOV component exposed via HTTP to untrusted networks.
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 the applicable Oracle Critical Patch Update for CVE-2024-21034 to all affected Oracle E-Business Suite instances (versions 12.2.3-12.2.13). Restrict HTTP access to the affected module via network segmentation or web application firewall rules as an interim control.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21034 — 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-21034 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