CVE-2024-21022
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 E-Business Suite versions 12.2.3-12.2.13. The vulnerability allows remote attackers to read, update, insert, or delete data through the LOV component via HTTP, requiring human interaction (likely a social engineering or click-based attack). The scope change indicates the attack can impact other Oracle products beyond the initial target.
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.
-
Verify E-Business Suite versionQuery the Oracle E-Business Suite version information using the standard version check utilities or by examining the application banner via the HTTP interfaceAffected if The installed version falls within the range 12.2.3 to 12.2.13 inclusive
-
Confirm CMRO module installationCheck if the Oracle Complex Maintenance, Repair, and Overhaul (CMRO) module is installed and enabled in the E-Business Suite instanceAffected if The CMRO module is present in the environment
-
Identify LOV component accessibilityDetermine if the List of Values (LOV) component is accessible via HTTP endpoints on the E-Business Suite serverAffected if The LOV component is exposed over HTTP without proper access controls
-
Assess HTTP endpoint exposureCheck whether the E-Business Suite HTTP endpoints are reachable from untrusted networksAffected if The HTTP interface is exposed to untrusted or external network sources
The environment is affected if it runs Oracle E-Business Suite version 12.2.3 through 12.2.13 with the CMRO module installed and the LOV component accessible via HTTP to untrusted sources.
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 (CPU) for April 2024 (or subsequent if available). As an interim control, restrict network access to the E-Business Suite HTTP endpoints to trusted sources only, and consider deploying a WAF with rules for the LOV component.
- Log in to My Oracle Support (https://support.oracle.com)
- Search for CVE-2024-21022 or the Oracle E-Business Suite Critical Patch Update for the quarter containing the fix
- Download and review the applicable security patch documentation for Oracle Complex Maintenance, Repair, and Overhaul
- Apply the patch following Oracle's standard EBS patch application procedures: backup the environment, run adpatch or similar tools, and verify the patch was applied successfully
- Test the LOV component functionality to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21022 — 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-21022 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