CVE-2020-14834
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 · uneditedVulnerability 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 confidenceVulnerability in the Oracle Trade Management User Interface component of Oracle E-Business Suite (versions 12.1.1-12.1.3 and 12.2.3-12.2.10). Unauthenticated remote attackers can exploit this via HTTP to gain unauthorized access to critical data or complete data access, plus unauthorized update/insert/delete operations. The requirement for human interaction suggests a client-side attack vector such as reflected XSS.
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>= 12.1.1, <= 12.1.3>= 12.2.3, <= 12.2.10CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Oracle E-Business Suite installationCheck if Oracle E-Business Suite is installed in your environment by looking for Oracle application binaries, services, or documentation. Common locations include $ORACLE_HOME and Oracle Application Object Library structures.Affected if Oracle E-Business Suite is not installed - you are not affected by this CVE.
-
Identify Oracle Trade Management versionQuery the Oracle Applications tables for the Trade Management version. In a standard Oracle E-Business Suite installation, you can check the version using SQL query: SELECT release_name FROM apps.fnd_product_groups WHERE application_id = (SELECT application_id FROM apps.fnd_application WHERE application_short_name = 'OKC'); Or check the version through Oracle Application Manager.Affected if The version falls outside the ranges 12.1.1-12.1.3 or 12.2.3-12.2.10 - you are not affected.
-
Verify Trade Management module is enabledCheck if the Oracle Trade Management module (OKC) is enabled and configured. This can be done through Oracle Application Manager > Security > Responsibility, or by checking if the OKC schema exists in the database and is accessible.Affected if The Trade Management module is not installed or enabled - the vulnerability cannot be exploited.
-
Check network exposure of Trade Management UIDetermine if the Trade Management User Interface is accessible over HTTP/HTTPS from untrusted networks. Review your web server configuration, load balancer rules, and firewall policies that expose Oracle E-Business Suite paths such as /OA_HTML/ or /okc/ endpoints.Affected if The Trade Management UI is exposed to unauthenticated remote attackers on untrusted networks - you are likely affected.
-
Inspect HTTP endpoints for XSS vulnerabilityReview the Trade Management UI HTTP endpoints for reflected XSS parameters. Common Oracle E-Business Suite paths for Trade Management include /OKC/../OA_HTML/ or similar. Use a web proxy or review access logs for unusual query parameters in requests to Trade Management URLs.Affected if You observe reflected parameters in Trade Management URLs that are echoed back without proper sanitization - you are likely affected.
Your environment is affected if Oracle E-Business Suite with Trade Management is installed, the version falls within 12.1.1-12.1.3 or 12.2.3-12.2.10, and the Trade Management UI is network-accessible to unauthenticated attackers.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update to address this vulnerability in the Trade Management UI component. Review and restrict network access to Oracle Trade Management interfaces as a compensating control until the patch can be applied.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14834 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14834 in production — separate from our analysis above.
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.
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.
- 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