CVE-2024-21016
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 confidenceOracle E-Business Suite Complex Maintenance, Repair, and Overhaul contains a vulnerability in the List of Values (LOV) component. The flaw is exploitable via HTTP without authentication but requires human interaction (such as clicking a malicious link). Successful exploitation allows unauthorized read, insert, update, or delete access to a subset of accessible data.
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 the Oracle E-Business Suite versionLog into Oracle E-Business Suite as a system administrator and navigate to the 'About Oracle Applications' page, or query the FND_PRODUCT_GROUPS table to retrieve the current version. Alternatively, check the VERSION file in the APPL_TOP directory if direct server access is available.Affected if The reported version falls within the range of 12.2.3 to 12.2.13 inclusive.
-
Confirm the Complex Maintenance Repair And Overhaul module is installedQuery the Oracle database for the presence of CMRO-related tables or modules. In the application, navigate to the 'Complex Maintenance, Repair and Overhaul' responsibility or check the installed modules via Oracle Application Manager.Affected if The CMRO module is present and accessible in the Oracle E-Business Suite environment.
-
Verify HTTP access to the application is enabledCheck the Oracle E-Business Suite listener configuration (such as the OHS or Apache configuration files in the Web tier) to confirm HTTP ports are active. Verify that the application is reachable via HTTP protocol rather than HTTPS only.Affected if HTTP access is enabled and the application is accessible over HTTP (port 8000, 8080, or similar).
-
Determine if the List of Values (LOV) component is accessibleAttempt to access any LOV field within the CMRO module through the web interface. This can be done by navigating to any form in CMRO that uses a List of Values, such as a lookup field.Affected if LOV functionality is operational and returns values through the web interface.
-
Review access controls on the LOV componentExamine the Oracle E-Business Suite responsibility and user definitions to determine the current user access levels. Check if the CMRO responsibilities are assigned to users without proper restriction.Affected if Users with minimal privileges can access CMRO functions and the LOV component returns data beyond their intended scope.
A system is affected if it runs Oracle E-Business Suite version 12.2.3 through 12.2.13 with the Complex Maintenance, Repair, and Overhaul module installed and accessible via HTTP, as the vulnerability allows unauthorized data access through the LOV component without 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 the relevant Oracle Critical Patch Update (CPU) for CVE-2024-21016. Since human interaction is required, user awareness training and restricting HTTP access to trusted sources may provide additional defense-in-depth mitigation.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21016 — 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-21016 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