Complex Maintenance\, Repair\, And OverhaulApplication · Oracle

CVE-2021-2103

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

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

dbcve analysis · high confidence

Unauthenticated remote vulnerability in Oracle Complex Maintenance, Repair, and Overhaul (CMRO) Dialog Box component. Attackers can exploit via HTTP without credentials but require human interaction (social engineering victim to click malicious link). The vulnerability enables unauthorized access to critical/confidential data and partial data modification (insert/update/delete) due to improper input validation or access control in dialog box functionality. Changed scope (S:C) indicates attack may impact additional products beyond the directly affected component.

MitigationApply Oracle Critical Patch Update (CPU) for January 2021. As immediate mitigation, restrict network access to CMRO application to trusted networks only, and implement additional authentication layers or web application firewall rules to detect and block malicious dialog box requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

Complex Maintenance\, Repair\, And OverhaulApplication

Affected:= 12.1= 12.2

Complex Maintenance Repair And OverhaulApplication

Affected:= 11.5.10

CVSS breakdown

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?

dbcve checks

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

Confirm Oracle CMRO installation and version

Query the Oracle Applications database or check Oracle Applications Manager (OAM) for the installed version of Oracle Complex Maintenance, Repair, and Overhaul. Use SQL query: SELECT product_version FROM apps.fnd_product_installations WHERE product LIKE '%CMRO%'; or access OAM homepage to view installed components.

Affected if Version is 11.5.10, 12.1.x, or 12.2.x (any subversion within these major releases)
Verify HTTP listener exposure for CMRO

Check Oracle HTTP Server (OHS) configuration files (httpd.conf, Oracle WebCache config) or Oracle E-Business Suite wireless/portlet configuration to confirm CMRO is accessible via HTTP/HTTPS protocols.

Affected if CMRO Dialog Box component is reachable over HTTP without additional authentication layers
Check network accessibility of CMRO application

Review network configuration, load balancer rules, or DMZ settings to determine if the CMRO application endpoint is exposed to network segments outside trusted internal networks. Use commands like: netstat -an | grep LISTEN | grep <CMRO port> or review firewall rules.

Affected if CMRO HTTP endpoints are accessible from untrusted network segments or the internet
Inspect dialog box component configuration

Access CMRO application administration console or configuration files (typically in $APPL_TOP or Oracle Application Server config) to verify if the Dialog Box functionality is enabled and accessible without proper access control restrictions.

Affected if Dialog Box component is enabled and accessible to unauthenticated or low-privilege users via HTTP requests
Review Oracle E-Business Suite patch level

Query Oracle inventory for applied patches using: opatch lsinventory -jdk $ORACLE_HOME/jdk or check Oracle Applications Manager for the January 2021 Critical Patch Update status.

Affected if The January 2021 CPU patch (or specific CVE-2021-2103 patch) has not been applied to the CMRO installation

The environment is affected if Oracle CMRO versions 11.5.10, 12.1, or 12.2 are installed AND the Dialog Box component is accessible via HTTP without proper authentication controls and the January 2021 CPU has not been applied.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply Oracle Critical Patch Update (CPU) for January 2021. As immediate mitigation, restrict network access to CMRO application to trusted networks only, and implement additional authentication layers or web application firewall rules to detect and block malicious dialog box requests.

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-2103 — 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

Primary sources

www.oracle.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2021-2103?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 8.2 High

Exploit likelihood EPSS, next 30 days 1.3%

Affects: Complex Maintenance\, Repair\, And Overhaul

Remediation

A high-priority fix

Fix this in Complex Maintenance\, Repair\, And Overhaul 28 hrs · Moderate

Typical engagement from $4,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2021-2103 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References