dbcve.org
Trade ManagementApplication · Oracle

CVE-2020-14876

CRITICAL · 9.1 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Trade Management product of Oracle E-Business Suite (component: User Interface). Supported versions that are affected are 12.1.1 - 12.1.3 and 12.2.3 - 12.2.10. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Trade Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Trade Management accessible data as well as unauthorized access to critical data or complete access to all Oracle Trade Management accessible data. CVSS 3.1 Base Score 9.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 Trade Management's User Interface component allows attackers with network access via HTTP to create, delete, or modify critical data, as well as gain unauthorized read access to all accessible data. The vulnerability affects versions 12.1.1-12.1.3 and 12.2.3-12.2.10 of the Oracle E-Business Suite component.

MitigationApply Oracle Critical Patch Update (CPU) for October 2020 or later. If immediate patching is not feasible, restrict network access to Oracle Trade Management interfaces at the network perimeter and monitor for unauthorized access patterns.

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
Trade ManagementApplication
Affected:>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Oracle Trade Management is installed
    Query the Oracle E-Business Suite database for the existence of the Trading Management module, or check the E-Business Suite registered applications for the Trade Management product.
    Affected if The product is not found in the registered applications.
  2. Check the Oracle E-Business Suite version
    Use the E-Business Suite version command or check the context file to obtain the current installation version number.
    Affected if The installed version falls within 12.1.1 through 12.1.3, or 12.2.3 through 12.2.10.
  3. Verify the Trade Management UI is network accessible
    Confirm that the Trade Management web interfaces (typically accessible through the E-Business Suite servlet ports) are reachable over HTTP/HTTPS from the network.
    Affected if The UI is exposed and the version is within the affected range.
  4. Check for unauthorized access patterns
    Review web access logs and Oracle E-Business Suite audit trails for unexpected POST requests to Trade Management UI endpoints from unauthenticated or unauthorized sources.
    Affected if Unauthenticated requests to Trade Management endpoints are observed in the logs.

A user is affected if Oracle Trade Management is installed and the E-Business Suite version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10 with the UI component network-accessible.

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
Upgrade available Upgrade to a release after 12.2.10
Interim mitigation

Apply Oracle Critical Patch Update (CPU) for October 2020 or later. If immediate patching is not feasible, restrict network access to Oracle Trade Management interfaces at the network perimeter and monitor for unauthorized access patterns.

Fix this in Trade Management 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 the upgrade done

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-2020-14876 — 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-2020-14876 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