dbcve.org
Trade ManagementApplication · Oracle

CVE-2020-14665

CRITICAL · 9.1 CVSS v3.1 Published 2020-07-15
Fix available
A fix is available. Upgrade to after 12.2.9 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: Invoice). Supported versions that are affected are 12.1.1-12.1.3 and 12.2.3-12.2.9. 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

Critical unauthenticated vulnerability in Oracle Trade Management Invoice component allows remote attackers via HTTP to create, delete, modify, or access all critical data in the affected Oracle E-Business Suite module. The flaw is easily exploitable with no authentication required and impacts both confidentiality and integrity.

MitigationApply Oracle Critical Patch Update (CPU) released July 2020 or later to address CVE-2020-14665 in affected Oracle Trade Management versions 12.1.1-12.1.3 and 12.2.3-12.2.9. Test thoroughly in non-production before production deployment.

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.9

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: SELECT product_version, patch_level FROM fnd_product_installations WHERE product LIKE '%Trade%'; Or check via Oracle Applications Manager (OAM) console.
    Affected if No Oracle Trade Management product is found in the environment.
  2. Verify Trade Management version
    Run: sqlplus APPS/<password> @$APPL_TOP/admin/adoverflow.sql or check the patch level via: SELECT patch_level FROM fnd_product_installations WHERE product LIKE '%ARX%' OR product LIKE '%OKS%'; Compare the version against 12.1.1-12.1.3 or 12.2.3-12.2.9.
    Affected if The installed version falls within 12.1.1 to 12.1.3 OR 12.2.3 to 12.2.9.
  3. Confirm the Invoice component is enabled
    Query: SELECT enabled_flag FROM fnd_menu_entries_vl WHERE menu_name = 'ARXINVOICE' OR function_name LIKE '%Invoice%'; Or check via Oracle Forms: Log into Trade Management and navigate to Invoice workbench.
    Affected if The Invoice module (ARXINVOICE) is accessible and enabled in the system.
  4. Check HTTP access exposure to Trade Management
    Review web listener configuration in $ORACLE_HOME/ Apache/ config files (httpd.conf, oracle_apache.conf) for Trade Management servlet mappings. Confirm if /ar/* or /oa_servlets/ routes are publicly accessible.
    Affected if HTTP access to Trade Management URLs is enabled and exposed (not restricted to internal networks or VPN).

The environment is affected if Oracle Trade Management version is 12.1.1-12.1.3 or 12.2.3-12.2.9, the Invoice component is enabled, and HTTP listeners are accessible to attackers.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 12.2.9
Interim mitigation

Apply Oracle Critical Patch Update (CPU) released July 2020 or later to address CVE-2020-14665 in affected Oracle Trade Management versions 12.1.1-12.1.3 and 12.2.3-12.2.9. Test thoroughly in non-production before production deployment.

Recommended fix High confidence

Upgrade to Oracle E-Business Suite 12.2.10 or later (12.2.x latest stable release)

  1. 1. Review Oracle E-Business Suite Supported Upgrade Paths documentation to confirm upgrade feasibility from your current version
  2. 2. Back up the entire Oracle E-Business Suite database and application tier before making any changes
  3. 3. Upgrade Oracle Trade Management from affected version (12.1.1-12.1.3 or 12.2.3-12.2.9) to version 12.2.10 or later
  4. 4. Alternatively, apply the Oracle Critical Patch Update (CPU) that addresses CVE-2020-14665 - check Oracle's July 2020 CPU or subsequent CPU for this fix
  5. 5. After upgrade/patch, verify the Invoice component is functioning correctly
  6. 6. Test that the vulnerability is no longer exploitable by reviewing access controls on the Invoice functionality
  7. 7. Apply any additional related security patches recommended in the same CPU
Caveat Oracle E-Business Suite upgrades may require significant testing of integrated modules; ensure regression testing covers Trade Management Invoice functionality and related workflows

Generated from the published advisory — verify against the referenced sources before acting.

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