dbcve.org
Advanced Outbound TelephonyApplication · Oracle

CVE-2020-2852

HIGH · 8.2 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
89/100
Remediation priority · High
High EPSS 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 Advanced Outbound Telephony product of Oracle E-Business Suite (component: Calendar). Supported versions that are affected are 12.1.1-12.1.3. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Advanced Outbound Telephony. Successful attacks require human interaction from a person other than the attacker and 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.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 · high confidence

Vulnerability in Oracle Advanced Outbound Telephony Calendar component (versions 12.1.1-12.1.3) allowing unauthenticated attackers with network access via HTTP to compromise the system. Requires human interaction from a victim user to exploit. Successful attacks grant unauthorized access to critical or all accessible data, plus unauthorized update/insert/delete access to some data. Scope change indicates attacks may impact additional Oracle products.

MitigationApply Oracle Critical Patch Update (CPU) for January 2020 or later. Until patch is applied, restrict network access to Oracle Advanced Outbound Telephony interfaces and monitor for suspicious calendar-related HTTP requests.

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
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 the Oracle E-Business Suite environment. The Advanced Outbound Telephony component is part of Oracle E-Business Suite. Check for Oracle application server processes and the presence of Oracle E-Business Suite directories.
    Affected if Oracle E-Business Suite with Advanced Outbound Telephony module is installed
  2. Check Advanced Outbound Telephony version
    Query the Oracle applications version table or use the Oracle ADministration utilities to retrieve the installed version of the Advanced Outbound Telephony module. Common methods include checking the version information through Oracle Applications Manager (OAM) or querying the relevant AOL version tables.
    Affected if Version falls within 12.1.1 through 12.1.3 inclusive
  3. Verify Calendar component is configured
    Check if the Calendar functionality within Advanced Outbound Telephony is enabled. This can be done by examining the Oracle Responsibilities and Functions assigned to users, or checking the Oracle Application Framework configuration for the Calendar module.
    Affected if Calendar component is enabled and accessible to users
  4. Assess HTTP network exposure
    Determine if the Oracle E-Business Suite web interfaces (specifically the Advanced Outbound Telephony Calendar URLs) are exposed to untrusted networks. Check firewall rules, load balancer configurations, and web server access controls for the Oracle applications HTTP endpoints.
    Affected if System is accessible over HTTP from untrusted networks without proper network segmentation

A system is affected if it runs Oracle Advanced Outbound Telephony versions 12.1.1 through 12.1.3 with the Calendar component enabled and exposed to network access via HTTP.

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 (CPU) for January 2020 or later. Until patch is applied, restrict network access to Oracle Advanced Outbound Telephony interfaces and monitor for suspicious calendar-related HTTP requests.

Fix this in Advanced Outbound Telephony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,800
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,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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