dbcve.org
Complex Maintenance\, Repair\, And OverhaulApplication · Oracle

CVE-2021-2104

HIGH · 8.2 CVSS v3.1 Published 2021-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Vulnerability in the Oracle Complex Maintenance, Repair, and Overhaul product of Oracle Supply Chain (component: Dialog Box). Supported versions that are affected are 11.5.10, 12.1 and 12.2. 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. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle Complex Maintenance, Repair, and Overhaul accessible data as well as unauthorized update, insert or delete access to some of Oracle Complex Maintenance, Repair, and Overhaul accessible data. CVSS 3.1 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 confidence

This is a dialog box component vulnerability in Oracle Complex Maintenance, Repair, and Overhaul (part of Oracle E-Business Suite). It is an easily exploitable flaw, likely cross-site scripting (XSS), allowing unauthenticated network attackers to compromise the component via HTTP. Successful exploitation requires human interaction (tricking a user to click a malicious link) and can lead to high confidentiality impact (access to critical data) and low integrity impact (unauthorized modifications).

MitigationApply Oracle Critical Patch Update (CPU) for January 2021 that addresses CVE-2021-2104. Review and test all dialog box interactions post-patch to confirm remediation.

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
Complex Maintenance\, Repair\, And OverhaulApplication
Affected:= 12.1= 12.2
Complex Maintenance Repair And OverhaulApplication
Affected:= 11.5.10

CVSS 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
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Oracle E-Business Suite with CMRO module is installed
    Check your Oracle applications inventory or E-Business Suite instance for the presence of the Complex Maintenance, Repair, and Overhaul (CMRO) module. This is typically found in the Oracle E-Business Suite application stack.
    Affected if The CMRO module is not installed or is from a different Oracle product line.
  2. Identify the CMRO version number
    Access the Oracle E-Business Suite administration screens or use the standard Oracle version query (typically via SQL: SELECT patch_level FROM apps.fnd_product_installations WHERE patch_level LIKE '%CMRO%'; or check the about page within the CMRO module).
    Affected if The installed version is 12.1.x, 12.2.x, or 11.5.10.
  3. Verify HTTP access to the dialog box component
    Determine if the CMRO web interface is accessible over HTTP/HTTPS from the network. Check the Oracle Applications Manager (OAM) or the web entry points for the CMRO module.
    Affected if The CMRO module is exposed via HTTP/HTTPS and accessible to unauthenticated network users.
  4. Confirm if the vulnerability is patchable
    Check if the January 2021 CPU has been applied. In Oracle E-Business Suite, this can be verified via the Oracle Applications Manager patch advisor or by checking the applied patches list for the January 2021 CPU.
    Affected if The January 2021 Critical Patch Update has NOT been applied and the CMRO version matches the affected versions.

A user is affected if they have Oracle CMRO versions 12.1, 12.2, or 11.5.10 installed with HTTP-accessible dialog box functionality and the January 2021 CPU has not been applied.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for January 2021 that addresses CVE-2021-2104. Review and test all dialog box interactions post-patch to confirm remediation.

Fix this in Complex Maintenance\, Repair\, And Overhaul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2104 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-2104 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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