dbcve.org
Advanced Outbound TelephonyApplication · Oracle

CVE-2020-2863

HIGH · 8.5 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable 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 Advanced Outbound Telephony product of Oracle E-Business Suite (component: User Interface). Supported versions that are affected are 12.1.1-12.1.3. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. While the vulnerability is in Oracle Advanced Outbound Telephony, 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 Advanced Outbound Telephony accessible data as well as unauthorized update, insert or delete access to some of Oracle Advanced Outbound Telephony accessible data. CVSS 3.0 Base Score 8.5 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/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

Vulnerability in Oracle Advanced Outbound Telephony User Interface component affecting versions 12.1.1-12.1.3. Easily exploitable via HTTP by low-privileged attackers, allowing unauthorized read access to critical data and partial write/delete access to some accessible data. The changed scope indicates potential impact beyond the directly affected product.

MitigationApply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2863. If patching is delayed, restrict network access to Oracle E-Business Suite HTTP interfaces and enforce least-privilege user access controls.

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
Advanced Outbound TelephonyApplication
Affected:>= 12.1.1, <= 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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Locate Oracle Advanced Outbound Telephony installation
    Check Oracle E-Business Suite inventory files or look for the Advanced Outbound Telephony module in the Oracle application directory structure (typically under $APPL_TOP or specific OAHT directories)
    Affected if The component is installed and running on the system
  2. Identify installed version of Oracle Advanced Outbound Telephony
    Query the Oracle database or check version files within the Advanced Outbound Telephony module directory. Look for version manifests or patches applied to the OAHT component
    Affected if Version is 12.1.1, 12.1.2, or 12.1.3 (within the 12.1.1-12.1.3 range)
  3. Verify HTTP interface exposure
    Check network listener configuration (Oracle HTTP Server or Oracle Apache) for endpoints serving the Advanced Outbound Telephony User Interface. Review httpd.conf or Oracle Web Listener configuration for OAHT-related servlet mappings
    Affected if HTTP interfaces for the Advanced Outbound Telephony UI are accessible over network (not restricted to localhost or VPN)
  4. Review access logs for UAOT UI endpoints
    Examine Oracle HTTP Server access logs and Oracle E-Business Suite diagnostic logs for unusual or unauthorized access patterns to /oaht/* or /crm/* endpoints, particularly from low-privileged users
    Affected if Logs show unexpected access from untrusted sources or unauthorized user sessions to UAOT endpoints

System is affected if Oracle Advanced Outbound Telephony User Interface version 12.1.1-12.1.3 is installed and its HTTP interface 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.1.3
Interim mitigation

Apply Oracle Critical Patch Update (April 2020) addressing CVE-2020-2863. If patching is delayed, restrict network access to Oracle E-Business Suite HTTP interfaces and enforce least-privilege user access controls.

Fix this in Advanced Outbound Telephony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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