dbcve.org
Trade ManagementApplication · Oracle

CVE-2020-14851

HIGH · 8.2 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 12.2.10 or later.
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 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 require human interaction from a person other than the attacker and while the vulnerability is in Oracle Trade Management, 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 Trade Management accessible data as well as unauthorized update, insert or delete access to some of Oracle Trade Management 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 HTTP vulnerability in Oracle Trade Management User Interface allows remote attackers to access critical data or gain unauthorized update/insert/delete privileges. Requires human interaction (social engineering) to trigger. The scope change flag indicates attacks may impact additional products beyond Trade Management.

MitigationApply Oracle Critical Patch Update addressing CVE-2020-14851. Since human interaction is required, combine with user security awareness training and restrict network access to the Trade Management interface.

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
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 Trade Management installation
    Locate the Oracle Trade Management application components in the Oracle E-Business Suite. Check for the presence of the 'TRADE MANAGEMENT' module in the Oracle Applications Manager (OAM) or via the AD Administration utility.
    Affected if The Oracle Trade Management module is present in the environment.
  2. Identify installed Trade Management version
    Query the Oracle Applications version table (FND_APPLICATION or FND_PRODUCT_INSTALLATIONS) to retrieve the exact version number of the Trade Management component, or use Oracle iSetup to export version information.
    Affected if The installed version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.10.
  3. Verify HTTP interface accessibility
    Confirm that the Trade Management User Interface is accessible via HTTP/HTTPS. Check the Oracle E-Business Suite profile option 'ICX: forms launcher' and the web listener configuration to determine if the /tradeManagement endpoint or related servlets are exposed.
    Affected if The Trade Management HTTP interface is reachable over the network.
  4. Review access logs for suspicious requests
    Examine Oracle HTTP Server access logs and Oracle WebLogic access logs for unusual or unauthorized requests to Trade Management URLs, particularly those involving data manipulation endpoints (update, insert, delete operations) from unexpected sources.

The environment is affected if Oracle Trade Management is installed AND the version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10 AND the HTTP interface is 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 addressing CVE-2020-14851. Since human interaction is required, combine with user security awareness training and restrict network access to the Trade Management interface.

Fix this in Trade Management Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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