dbcve.org
Advanced Outbound TelephonyApplication · Oracle

CVE-2020-14670

HIGH · 8.2 CVSS v3.1 Published 2020-07-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 Advanced Outbound Telephony product of Oracle E-Business Suite (component: Settings). 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 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.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 · moderate confidence

Unauthenticated vulnerability in Oracle Advanced Outbound Telephony's Settings component allows remote attackers via HTTP to access critical data or gain full access to all accessible data, plus unauthorized update/insert/delete operations on some data. Requires human interaction (UI:R) and scope change (S:C) indicates impact to additional products beyond the vulnerable component.

MitigationApply Oracle Critical Patch Update (CPU) for CVE-2020-14670 to the affected Oracle E-Business Suite versions (12.1.1-12.1.3, 12.2.3-12.2.9). Since this is an unauthenticated vulnerability, prioritize patching immediately and restrict HTTP access to the Settings component via network segmentation or WAF rules as an interim control.

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>= 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 if Oracle Advanced Outbound Telephony is installed
    Check the Oracle E-Business Suite application modules. In Oracle Applications Manager (OAM) or via SQL query against FND_PRODUCT_INSTALLATIONS table, look for the Advanced Outbound Telephony product component.
    Affected if The product component is not found in the system, then not affected.
  2. Determine the installed version of Oracle Advanced Outephony
    Query the version through Oracle Applications Manager or check the Oracle E-Business Suite version banner. The version format will be in the 12.1.x or 12.2.x family.
    Affected if The installed version falls within 12.1.1 through 12.1.3 inclusive, or 12.2.3 through 12.2.9 inclusive.
  3. Verify HTTP access is enabled for the Settings component
    Check the Oracle E-Business Suite listener configuration (Oracle HTTP Server or Apache). Determine if the /oa_html/ or /OA_HTML/ paths serving the Advanced Outbound Telephony Settings component are exposed via HTTP listener.
    Affected if HTTP access is enabled and the Settings component URL path is reachable over HTTP without authentication.
  4. Confirm the Settings component is accessible without authentication
    Attempt to access the Advanced Outbound Telephony Settings URL path (typically under the OA_HTML directory for Oracle Applications) via HTTP without providing credentials. If the page loads or returns data without login, the vulnerability is present.
    Affected if The Settings component returns data or allows operations without requiring authentication.

A system is affected if Oracle Advanced Outbound Telephony is installed with version 12.1.1-12.1.3 or 12.2.3-12.2.9 AND the Settings component is accessible via HTTP without authentication.

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 Critical Patch Update (CPU) for CVE-2020-14670 to the affected Oracle E-Business Suite versions (12.1.1-12.1.3, 12.2.3-12.2.9). Since this is an unauthenticated vulnerability, prioritize patching immediately and restrict HTTP access to the Settings component via network segmentation or WAF rules as an interim control.

Fix this in Advanced Outbound Telephony Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
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,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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