dbcve.org
Customer Interaction HistoryApplication · Oracle

CVE-2021-2105

HIGH · 8.2 CVSS v3.1 Published 2021-01-20
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 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.10. 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.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

CVE-2021-2105 is an unauthenticated HTTP vulnerability in Oracle Customer Interaction History (Outcome-Result component) affecting E-Business Suite versions 12.1.1-12.1.3 and 12.2.3-12.2.10. An unauthenticated remote attacker can exploit this via HTTP to gain unauthorized access to critical/confidential data and perform unauthorized updates/inserts/deletes. Exploitation requires human interaction (phishing/social engineering), and while limited to Oracle Customer Interaction History, attacks may impact additional products due to scope change.

MitigationApply Oracle Critical Patch Update (CPU) for January 2021 or later. Additionally, restrict HTTP/HTTPS exposure to only trusted networks, implement WAF rules, and train users to recognize phishing attempts given the required user interaction for exploitation.

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.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. Identify Oracle E-Business Suite installation
    Check if Oracle E-Business Suite is installed by querying the database for APPS schema version or checking $APPL_TOP directory for version files. Run: sqlplus apps/@{SID} 'SELECT release_name FROM apps.fnd_product_groups;'
    Affected if Version matches 12.1.1 through 12.1.3 or 12.2.3 through 12.2.10
  2. Confirm Oracle Customer Interaction History component
    Check if Oracle Customer Interaction History (Outcome-Result component) is installed and enabled. Query: SELECT task_type, task_name FROM ci_history_tasks WHERE ROWNUM <= 10; or check the Oracle Applications Manager console for installed modules.
    Affected if The Outcome-Result component (ci_history_tasks table or CI_HISTORY module) exists in the environment
  3. Verify HTTP listener exposure
    Check if Oracle HTTP Server or Oracle Application Server is serving the /oa_servlets/ or /webservices/ paths accessible externally. Review the Oracle HTTP Server configuration files (httpd.conf, apps.conf) and test external connectivity using: curl -I https://yourdomain.com/
    Affected if HTTP/HTTPS ports 80/443 or the /oa_servlets/ endpoint is accessible from untrusted networks
  4. Review web access logs for suspicious patterns
    Examine Apache/Oracle HTTP Server access logs (in $LOG_HOME/ora/ or $ORACLE_HOME/Apache/Apache/logs/) for repeated requests to /oa_servlets/ci/* endpoints, especially from untrusted IP ranges or unusual User-Agent strings.
    Affected if Unusual or repeated requests to Customer Interaction History servlets from unknown sources are found

The environment is affected if Oracle E-Business Suite version is 12.1.1-12.1.3 or 12.2.3-12.2.10 AND the Oracle Customer Interaction History component is installed AND HTTP is externally 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 January 2021 or later. Additionally, restrict HTTP/HTTPS exposure to only trusted networks, implement WAF rules, and train users to recognize phishing attempts given the required user interaction for exploitation.

Fix this in Customer Interaction History Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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