CVE-2024-21037
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 confidenceThis is an unauthenticated HTTP vulnerability in the List of Values (LOV) component of Oracle Complex Maintenance, Repair, and Overhaul (CMRO) in Oracle E-Business Suite versions 12.2.3-12.2.13. An attacker can exploit this without credentials by sending crafted HTTP requests, requiring only human interaction (such as clicking a link). The vulnerability allows partial unauthorized read and write access to CMRO data, and due to scope change, may impact additional Oracle 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.
-
Confirm Oracle E-Business Suite versionQuery the Oracle Applications database table FND_PRODUCT_INSTALLATIONS or check the applications context file (context_name.xml in $APPL_TOP/admin) to identify the installed EBS version. Alternatively, access Oracle Applications Manager (OAM) and navigate to the version information page.Affected if The installed version is between 12.2.3 and 12.2.13 inclusive.
-
Verify CMRO module is installedQuery the Oracle EBS product tables (such as FND_PRODUCT_GROUPS or CMCS_VISIBLE_PRODUCTS) to determine if the Complex Maintenance, Repair, and Overhaul (CMRO) module is registered as an installed product. In OAM, navigate to the Registered Products page to list installed modules.Affected if CMRO is listed as an installed or enabled module in the Oracle EBS environment.
-
Identify if LOV web interface is accessibleCheck the Oracle E-Business Suite web listener configuration (OHS/Oracle HTTP Server) for routes serving the LOV function. Typical paths include /OA_HTML/rlf/ or /webservices/loz/ endpoints. Review the mod_plsql configuration or WebGate setup for exposed LOV-related URLs.Affected if HTTP endpoints handling the List of Values (LOV) component are accessible from the network where attackers could send requests.
-
Review CMRO data access controlsExamine the CMRO application responsibilities and permissions assigned to public or unauthenticated user roles. Check if any CMRO-related responsibilities are accessible without authentication or assigned to the GUEST/ANONYMOUS user account.Affected if CMRO data or LOV functions can be accessed without valid authentication credentials.
A user is affected if their Oracle E-Business Suite installation runs version 12.2.3 through 12.2.13, has the CMRO module installed, and exposes the LOV component via accessible HTTP endpoints without requiring authentication.
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's Critical Patch Update (CPU) or specific patch for CVE-2024-21037 to the affected Oracle E-Business Suite installation. Prior to deployment, ensure current backups exist and plan for appropriate downtime; post-patch, thoroughly validate LOV functionality and related data access controls.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21037 — 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-21037 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