dbcve.org
Common ApplicationsApplication · Oracle

CVE-2020-14688

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 Common Applications product of Oracle E-Business Suite (component: CRM User Management Framework). 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 Common Applications. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Oracle Common Applications, 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 Common Applications accessible data as well as unauthorized update, insert or delete access to some of Oracle Common Applications 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 · high confidence

CVE-2020-14688 is an unauthenticated HTTP vulnerability in Oracle E-Business Suite's CRM User Management Framework (versions 12.1.3 and 12.2.3-12.2.9). Attackers with network access can exploit this flaw through HTTP requests, requiring human interaction to trigger the attack. The vulnerability allows unauthorized access to critical data or complete data access, as well as unauthorized modification (update/insert/delete) of some accessible data.

MitigationApply Oracle Critical Patch Updates (CPU) for the affected E-Business Suite versions. If patches are unavailable, implement network segmentation and restrict HTTP access to Oracle Common Applications through web application firewalls or access controls to reduce attack surface.

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
Common ApplicationsApplication
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
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
    Check for Oracle E-Business Suite processes running on the application server (such as Oracle HTTP Server, Oracle WebLogic, or Apache processes typically associated with EBS). Alternatively, review the application server configuration files and standard EBS installation directories.
    Affected if Oracle E-Business Suite is installed and running on the system
  2. Determine E-Business Suite version
    Locate and inspect the version file or context file in the EBS installation directory. The version is typically stored in the $APPL_TOP directory or can be retrieved using Oracle application administration tools (such as adident or SQL queries against the FND_PRODUCT_INSTALLATIONS table).
    Affected if The installed version matches 12.1.3 or falls within 12.2.3 through 12.2.9
  3. Verify CRM User Management Framework is enabled
    Check if the CRM User Management Framework module is configured and accessible. This can be done by reviewing the Oracle Applications Manager (OAM) console configuration, checking the enabled modules, or attempting to access the User Management Framework URL path (typically under /oa_servlets/ or /userManagement/ on the EBS instance).
    Affected if The CRM User Management Framework module is enabled and accessible in the E-Business Suite installation
  4. Confirm HTTP network exposure
    Determine if the EBS web interfaces (particularly the Oracle Application Framework pages) are exposed to the network beyond localhost. Review web server configuration files (such as Oracle HTTP Server httpd.conf or Oracle WebLogic configuration) and firewall rules to identify if the affected endpoints are reachable from external network addresses.
    Affected if The E-Business Suite HTTP interfaces are accessible from network addresses other than localhost or trusted internal hosts

The environment is affected if Oracle E-Business Suite version 12.1.3 or 12.2.3-12.2.9 is installed, the CRM User Management Framework is enabled, and the HTTP interface is exposed to the network.

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 Updates (CPU) for the affected E-Business Suite versions. If patches are unavailable, implement network segmentation and restrict HTTP access to Oracle Common Applications through web application firewalls or access controls to reduce attack surface.

Fix this in Common Applications Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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