dbcve.org
Customer Interaction HistoryApplication · Oracle

CVE-2020-2873

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.2.9 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 Customer Interaction History product of Oracle E-Business Suite (component: Outcome-Result). 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 Customer Interaction History. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Customer Interaction History, 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 Customer Interaction History accessible data as well as unauthorized update, insert or delete access to some of Oracle Customer Interaction History accessible data. CVSS 3.0 Base Score 8.2 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/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 · moderate confidence

This is an unauthenticated HTTP vulnerability in the Oracle Customer Interaction History Outcome-Result component, affecting E-Business Suite versions 12.1.1-12.1.3 and 12.2.3-12.2.9. The flaw allows remote attackers to gain unauthorized access to critical data or complete data access, plus unauthorized update/insert/delete operations on some accessible data. The requirement for human interaction (UI:R) and scope change (S:C) indicates the attack may involve social engineering or propagate to affect additional products beyond the targeted component.

MitigationApply Oracle's applicable Critical Patch Update (CPU) for CVE-2020-2873 when released. Until then, restrict network access to Oracle E-Business Suite interfaces and implement additional authentication layers for the Customer Interaction History module.

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
Customer Interaction HistoryApplication
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
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. Identify Oracle E-Business Suite installation
    Locate Oracle E-Business Suite middleware homes or application servers running the EBS web tier. Check for Oracle Application Server or Oracle WebLogic processes listening on HTTP/HTTPS ports.
    Affected if Oracle E-Business Suite is installed and accessible via network
  2. Determine E-Business Suite version
    Query the version of Oracle E-Business Suite using the Oracle Applications Manager interface, or check the $APPL_TOP/../patch/115/version directory, or query the FND_PRODUCT_GROUPS table if database access is available.
    Affected if Version falls within 12.1.1 to 12.1.3, or 12.2.3 to 12.2.9
  3. Check if Customer Interaction History module is configured
    Verify if the Oracle Customer Interaction History component is deployed and enabled. This may be visible in Oracle Application Manager under the Outcome-Result functionality, or accessible via the /oa_html/ or /OA_HTML/ web paths.
    Affected if Customer Interaction History Outcome-Result component is enabled and accessible
  4. Verify HTTP endpoint exposure
    Test access to the Customer Interaction History HTTP endpoints without authentication. Attempt to reach the component via the E-Business Suite web interface on ports 8000-8090 typical for EBS.
    Affected if Unauthenticated HTTP access to Customer Interaction History is possible from the network

If Oracle E-Business Suite versions 12.1.1-12.1.3 or 12.2.3-12.2.9 are running with Customer Interaction History accessible via HTTP without additional authentication, the environment is affected by CVE-2020-2873.

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

Apply Oracle's applicable Critical Patch Update (CPU) for CVE-2020-2873 when released. Until then, restrict network access to Oracle E-Business Suite interfaces and implement additional authentication layers for the Customer Interaction History module.

Fix this in Customer Interaction History Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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