CVE-2020-2856
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 · uneditedVulnerability 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 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 confidenceOracle Advanced Outbound Telephony UI component in E-Business Suite versions 12.1.1-12.1.3 contains a vulnerability exploitable via HTTP by unauthenticated remote attackers. Successful exploitation allows unauthorized access to critical data and unauthorized modification (insert/update/delete) of some accessible data, requiring human interaction (e.g., tricking a user into clicking a malicious link).
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>= 12.1.1, <= 12.1.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Oracle E-Business Suite installationQuery the database or check the APPL_TOP for Oracle E-Business Suite installation: SELECT product_version FROM apps.fnd_product_groups WHERE product_group_name LIKE 'E-Business Suite%'; or check $APPL_TOP/$APPLLOG for version files.Affected if E-Business Suite version is 12.1.x (12.1.1 through 12.1.3)
-
Locate Oracle Advanced Outbound Telephony componentCheck if the Advanced Outbound Telephony module is installed by querying: SELECT patch_level FROM apps.fnd_patch_service_levels WHERE patch_level LIKE '%Advanced%Outbound%'; or check the Oracle Applications Manager (OAM) for installed modules.Affected if The Advanced Outbound Telephony component is present in the E-Business Suite installation
-
Determine Advanced Outbound Telephony versionQuery the specific version of the Advanced Outbound Telephony module: SELECT a.application_name, b.release_name FROM apps.fnd_application a, apps.fnd_application_tl b WHERE a.application_id = b.application_id AND a.application_name LIKE '%Advanced%Outbound%'; or check the Oracle HTML DB interface for module version information.Affected if Version falls within range >= 12.1.1 and <= 12.1.3
-
Verify HTTP accessibility of the UI componentCheck if the Oracle Advanced Outbound Telephony web interface is accessible over HTTP/HTTPS by attempting to access the endpoint or reviewing web server configuration files in $IAS_ORACLE_HOME/Apache/Apache/conf for URL mappings to the Advanced Outbound Telephony module.Affected if The UI component is exposed via HTTP and accessible to network users
User is affected if Oracle E-Business Suite 12.1.x with Oracle Advanced Outbound Telephony component version 12.1.1-12.1.3 is installed and the UI is network-accessible via HTTP.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Oracle Critical Patch Update (CPU) patches for CVE-2020-2856 to Oracle E-Business Suite 12.1.x. Until patches are applied, restrict network access to the Oracle Advanced Outbound Telephony interface through network segmentation or web application firewall rules.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2020-2856 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2856 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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