dbcve.org
Trade ManagementApplication · Oracle

CVE-2020-14808

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.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-based vulnerability in Oracle Trade Management's User Interface component allows remote attackers to potentially access or modify critical data. The attack requires human interaction (likely CSRF or similar UI-based attack vector), and while primarily affecting Oracle Trade Management, it may impact additional Oracle E-Business Suite products due to shared components.

MitigationApply Oracle Critical Patch Update (CPU) for October 2020 or subsequent relevant patches addressing CVE-2020-14808 to all affected Oracle Trade Management installations (12.1.3, 12.2.3-12.2.10). Coordinate testing with business users to validate the fix given the human interaction attack vector.

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.2.3, <= 12.2.10= 12.1.3

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. Verify Oracle Trade Management is installed
    Check your Oracle E-Business Suite environment for the presence of the Oracle Trade Management module. Query the Oracle Applications tables (such as FND_APPLICATION or similar) to identify if the Trade Management product is registered.
    Affected if Oracle Trade Management (or a related EBS module sharing the UI component) is installed and exposed via HTTP/HTTPS
  2. Determine the installed version of Oracle Trade Management
    Query the Oracle version tables or use Oracle Application Manager to retrieve the exact version number of the Oracle Trade Management component. Compare the version against the affected ranges: 12.1.3, or 12.2.3 through 12.2.10.
    Affected if The installed version matches 12.1.3 or falls within 12.2.3 to 12.2.10 inclusive
  3. Check if the UI component is accessible over the network
    Identify whether the Oracle Trade Management User Interface is accessible via HTTP or HTTPS from external or untrusted networks. Review your web server configuration and load balancer rules to determine the exposure of the /oa or related Trade Management endpoints.
    Affected if The UI component is exposed to network access without proper authentication barriers or network segmentation
  4. Inspect for missing security configurations
    Review the Oracle E-Business Suite security configuration for the Trade Management module. Check whether Oracle's recommended security settings for the User Interface component are properly configured, including session management and CSRF protections.
    Affected if Security configurations for the UI are not properly hardened or CSRF protections are disabled or missing

Your environment is likely affected if Oracle Trade Management version 12.1.3 or any version from 12.2.3 to 12.2.10 is installed and its UI component 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 (CPU) for October 2020 or subsequent relevant patches addressing CVE-2020-14808 to all affected Oracle Trade Management installations (12.1.3, 12.2.3-12.2.10). Coordinate testing with business users to validate the fix given the human interaction attack vector.

Fix this in Trade Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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