Crm Technical FoundationApplication · Oracle

CVE-2020-14679

HIGH · 7.5 CVSS v3.1 Published 2020-07-15
Fix available
A fix is available. Upgrade to after 12.2.9 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 CRM Technical Foundation product of Oracle E-Business Suite (component: Preferences). Supported versions that are affected are 12.1.3 and 12.2.3-12.2.9. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle CRM Technical Foundation. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle CRM Technical Foundation. CVSS 3.1 Base Score 7.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).

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

This is an unauthenticated Denial of Service vulnerability in Oracle CRM Technical Foundation's Preferences component. An attacker with network access via HTTP can exploit this flaw to cause the application to hang or crash repeatedly. The vulnerability affects versions 12.1.3 and 12.2.3 through 12.2.9 of the Oracle E-Business Suite.

MitigationApply the relevant Oracle Critical Patch Update (CPU) or Security Patch Update (PSU) for CVE-2020-14679. As an immediate workaround, restrict network access to the affected Oracle CRM Technical Foundation endpoints where feasible.

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
Crm Technical FoundationApplication
Affected:>= 12.2.3, <= 12.2.9= 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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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. Confirm Oracle E-Business Suite installation
    Look for Oracle Application Server processes, check for Oracle E-Business Suite directories (typically $ORACLE_HOME/apps), or identify HTTP listeners on common ports (8000, 8001, 443, 80) serving Oracle applications.
    Affected if If Oracle E-Business Suite is installed and running
  2. Identify Oracle E-Business Suite version
    Check the version file in the Oracle Applications filesystem, or query the database for the release version using SQL: SELECT RELEASE_NAME FROM FND_PRODUCT_GROUPS; Alternatively, access the 'About Oracle Applications' page from the system administrator responsibility.
    Affected if If the version matches 12.1.3 or falls within 12.2.3 through 12.2.9
  3. Determine if web interfaces are network-accessible
    Test HTTP/HTTPS access to the Oracle E-Business Suite login page from external systems. Check firewall rules and load balancer configurations that expose the application ports (commonly 8000-8005, 80, 443).
    Affected if If the Oracle E-Business Suite web login is accessible from untrusted networks
  4. Verify Preferences component exposure
    Attempt to access the Preferences component endpoint via HTTP. Common paths include /OA_HTML/射频/preferences or similar endpoints under the /OA_HTML/ path. Check which modules are enabled in Oracle Application Manager.
    Affected if If the Preferences component is accessible without authentication via HTTP

A user is affected if they are running Oracle E-Business Suite versions 12.1.3 or 12.2.3-12.2.9 with the web interfaces network-accessible and the Preferences component enabled.

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 the relevant Oracle Critical Patch Update (CPU) or Security Patch Update (PSU) for CVE-2020-14679. As an immediate workaround, restrict network access to the affected Oracle CRM Technical Foundation endpoints where feasible.

Fix this in Crm Technical Foundation Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,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 $8,256.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-14679 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