CVE-2024-21044
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 confidenceOracle E-Business Suite Complex Maintenance, Repair, and Overhaul contains a vulnerability in the List of Values (LOV) component. An unauthenticated attacker with network access via HTTP can exploit this flaw to achieve unauthorized read, insert, update, or delete access to a subset of the application's data. The attack requires human interaction and may impact additional products due to scope change.
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 installationCheck for the presence of Oracle E-Business Suite by looking for its application directories (typically under $APPL_TOP or in Oracle WebLogic/Oracle HTTP Server paths) or by querying the Oracle database for EBS-related schema objects.Affected if Oracle E-Business Suite is not installed - the check does not apply
-
Identify the EBS version numberRun the command 'adident Header $AD_TOP/bin/adworker' or query the 'FND_PRODUCT_RELEASES' table in the Oracle database to retrieve the installed version of Oracle E-Business Suite.Affected if The installed version is greater than or equal to 12.2.3 AND less than or equal to 12.2.13 - the environment falls within the affected range
-
Verify Complex Maintenance, Repair, and Overhaul (CMRO) moduleCheck if the CMRO module is enabled by querying the 'FND_APPLICATION' or 'FND_PRODUCT_INSTALLATIONS' tables for 'ONT' (Oracle Order Management) or specific CMRO-related responsibilities, or by reviewing the EBS application module configuration.Affected if The CMRO/Complex Maintenance module is installed and enabled in the EBS environment
-
Confirm HTTP network accessibilityVerify that the Oracle E-Business Suite web interfaces (Oracle Application Server/Oracle HTTP Server) are accessible over HTTP/HTTPS on the configured port (typically 8000, 8001, or 443). Check the Oracle E-Business Suite context file or configuration files for web listener status.Affected if The EBS web interface is reachable via network HTTP/HTTPS requests - this allows the unauthenticated attacker to reach the LOV component
If Oracle E-Business Suite version 12.2.3 through 12.2.13 is installed with the CMRO module enabled and the web interface is network-accessible via HTTP, the environment is potentially affected by CVE-2024-21044.
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.
dbcve · scopedApply the Oracle Critical Patch Update for April 2024 that addresses CVE-2024-21044, or apply the relevant patch for Oracle E-Business Suite version 12.2.3-12.2.13. Oracle recommends reviewing the April 2024 Critical Patch Update and implementing all applicable security patches for the E-Business Suite installation.
Oracle E-Business Suite 12.2.14 or later
- 1. Review the Oracle E-Business Suite 12.2.14 release notes and upgrade considerations
- 2. Prepare a comprehensive test environment mirroring the production setup
- 3. Execute a full backup of the Oracle E-Business Suite database and application tier
- 4. Apply the Oracle E-Business Suite 12.2.14 upgrade in a non-production environment first
- 5. Validate all Critical Patch Update (CPU) fixes included in 12.2.14, specifically confirming CVE-2024-21044 is addressed
- 6. Run functional and integration tests for the Complex Maintenance, Repair, and Overhaul module
- 7. After successful testing, schedule production upgrade during maintenance window
- 8. Verify the LOV component and CSRF protections are functioning correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- 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-21044 — 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-21044 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