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

CVE-2021-2102

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 · high confidence

Unauthenticated remote vulnerability in Oracle Complex Maintenance, Repair, and Overhaul's Dialog Box component allowing injection of malicious content via HTTP. The attack requires human interaction (likely social engineering to click a crafted link), enabling attackers to execute unauthorized operations with the privileges of the victim's session, including unauthorized data access (high confidentiality impact) and partial data modification (low integrity impact).

MitigationApply the Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2102 to affected versions 11.5.10, 12.1, and 12.2. If immediate patching is not feasible, restrict network access to the affected Oracle application to trusted networks only, and educate users about not clicking untrusted links.

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. Identify installed Oracle CMRO version
    Query the Oracle Applications tables or use the Oracle Application Manager (OAM) to determine the exact version of Complex Maintenance, Repair, and Overhaul installed. Look for version strings 11.5.10, 12.1, or 12.2 in the Oracle E-Business Suite version information.
    Affected if The installed version matches 11.5.10, 12.1, or 12.2.
  2. Verify Dialog Box component is HTTP-accessible
    Check the Oracle Applications context file (context_name.xml in $APPL_TOP/admin) or Oracle HTTP Server configuration to confirm the Dialog Box component is exposed via HTTP/HTTPS endpoints accessible from the network.
    Affected if The Dialog Box component is enabled and reachable over HTTP without additional authentication layers.
  3. Review Oracle Fusion Middleware proxy configuration
    Inspect the Oracle WebLogic Server or Oracle HTTP Server configuration files (such as mod_wl_ohs.conf or httpd.conf) for any URL forwarding rules that expose the Dialog Box functionality to unauthenticated users.
    Affected if URL routing rules allow unauthenticated access to Dialog Box endpoints.
  4. Examine Oracle Applications listener security settings
    Check the Oracle Forms and Apache configuration files (specifically the forms.conf or app.conf) to determine if the Forms servlet that serves Dialog Box content has proper authentication enforcement.
    Affected if The Forms servlet or Dialog Box component lacks强制 authentication or uses weak access controls.
  5. Audit access logs for suspicious Dialog Box requests
    Review Oracle HTTP Server access logs (in $ORACLE_HOME/Apache/Apache/logs or equivalent) for anomalous GET/POST requests to Dialog Box-related URLs, particularly those containing unexpected parameters or encoded content.
    Affected if Logs show unauthorized or unexpected requests to Dialog Box endpoints from untrusted sources.

Your environment is affected if you run Oracle CMRO versions 11.5.10, 12.1, or 12.2 with the Dialog Box component exposed over HTTP to untrusted networks.

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 the Oracle Critical Patch Update (CPU) containing the fix for CVE-2021-2102 to affected versions 11.5.10, 12.1, and 12.2. If immediate patching is not feasible, restrict network access to the affected Oracle application to trusted networks only, and educate users about not clicking untrusted links.

Fix this in Complex Maintenance\, Repair\, And Overhaul Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-2102 — 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-2102 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