CVE-2024-21045
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 vulnerability in the List of Values (LOV) component of Oracle Complex Maintenance, Repair, and Overhaul allows remote attackers via HTTP to inject unauthorized database operations. The flaw permits unauthorized read, insert, update, and delete access to a subset of CMRO data without authentication, requiring human interaction to trigger.
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 CMRO module is installedCheck if Oracle Complex Maintenance, Repair, and Overhaul module is part of your Oracle E-Business Suite installation by querying the Oracle Applications tables or checking your EBS module licensing documentation.Affected if CMRO module is present in the environment
-
Check CMRO versionQuery the Oracle E-Business Suite version information for the CMRO module. This can typically be found in the Oracle Applications Manager interface or by checking the release version files specific to the CMRO patch level.Affected if Installed version falls within 12.2.3 through 12.2.13 inclusive
-
Verify HTTP access to CMRO Lov endpointInspect your web server configuration or reverse proxy rules to determine if the CMRO application URLs (specifically those handling List of Values functionality) are accessible via HTTP/HTTPS from the network.Affected if CMRO Lov URLs are network-accessible without additional authentication barriers beyond standard EBS login
-
Check for unauthenticated LOV request patternsReview HTTP access logs for CMRO application endpoints, specifically look for requests to LOV-related URLs that occur without corresponding authenticated session tokens or that originate from unexpected sources.Affected if LOV requests are logged from unauthenticated sources or without valid session credentials
The environment is affected if Oracle CMRO module is installed with version between 12.2.3 and 12.2.13 and the LOV component is accessible over the network.
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 Oracle Critical Patch Update for CVE-2024-21045 to Oracle E-Business Suite 12.2.3-12.2.13. Until patch availability, restrict network access to CMRO interfaces and monitor for suspicious LOV queries.
- 1. Navigate to Oracle My Oracle Support (https://support.oracle.com) and search for CVE-2024-21045
- 2. Download the applicable Oracle Critical Patch Update (CPU) for January 2024 or later that addresses this vulnerability
- 3. Review the patch matrix to confirm the patch applies to Oracle Complex Maintenance, Repair, and Overhaul version 12.2.3-12.2.13
- 4. Apply the patch following Oracle's standard E-Business Suite patch application procedures
- 5. Verify the patch was applied successfully by checking the applied patches in Oracle Applications Manager
- 6. Test the LOV component functionality to ensure normal operation after patch application
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-21045 — 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-21045 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