dbcve.org
Financial Services Analytical Applications InfrastructureApplication · Oracle

CVE-2020-14824

HIGH · 8.6 CVSS v3.1 Published 2020-10-21
Fix available
A fix is available. Upgrade to after 8.1.0.0.0 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Financial Services Analytical Applications Infrastructure product of Oracle Financial Services Applications (component: Infrastructure). Supported versions that are affected are 8.0.6-8.1.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle Financial Services Analytical Applications Infrastructure. While the vulnerability is in Oracle Financial Services Analytical Applications Infrastructure, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Financial Services Analytical Applications Infrastructure. CVSS 3.1 Base Score 8.6 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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

A vulnerability in Oracle Financial Services Analytical Applications Infrastructure (versions 8.0.6-8.1.0) allows unauthenticated remote attackers to cause a denial of service via HTTP requests. The vulnerability has a changed scope, meaning attacks may impact additional products beyond the directly affected component.

MitigationApply the Oracle patch for CVE-2020-14824 from Oracle's Critical Patch Updates. If a patch is unavailable, consider network segmentation and web application firewall rules to limit HTTP exposure to the affected infrastructure.

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
Financial Services Analytical Applications InfrastructureApplication
Affected:>= 8.0.6.0.0, <= 8.1.0.0.0

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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. Identify Oracle Financial Services Analytical Applications Infrastructure installation
    Locate the OFSAAI installation directory and check for presence of the financial services analytical applications infrastructure components. Common paths include $OFSAAI_HOME or standard Oracle application directories.
    Affected if The product is not installed - then not affected. If installed, proceed to version check.
  2. Determine installed version of OFSAAI
    Check the version file or configuration in the OFSAAI installation. Look for version files typically named version.txt, version.info, or check the About/Version information within the application administrative console.
    Affected if Installed version is between 8.0.6.0.0 and 8.1.0.0.0 (inclusive) - this indicates the environment falls within the affected version range.
  3. Verify HTTP exposure of the OFSAAI web interface
    Review network configuration to determine if the OFSAAI web application is exposed via HTTP/HTTPS to network segments outside the trusted internal network. Check web server configuration files (such as web.xml, httpd.conf, or Oracle WebLogic configuration) for accessible endpoints.
    Affected if The web interface is externally accessible or accessible from untrusted network segments - combined with affected version, this creates the conditions for exploitation.
  4. Check for recent security events or DoS indicators
    Review web server access logs and intrusion detection system logs for patterns of repeated HTTP requests that may indicate exploitation attempts against the OFSAAI endpoints.
    Affected if Log analysis shows unusual patterns of HTTP requests targeting OFSAAI endpoints, particularly from external sources.

A system is affected if Oracle Financial Services Analytical Applications Infrastructure version 8.0.6.0.0 through 8.1.0.0.0 is installed AND the HTTP-based web interface is network-accessible to untrusted users.

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 8.1.0.0.0
Interim mitigation

Apply the Oracle patch for CVE-2020-14824 from Oracle's Critical Patch Updates. If a patch is unavailable, consider network segmentation and web application firewall rules to limit HTTP exposure to the affected infrastructure.

Fix this in Financial Services Analytical Applications Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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 locally
dbcve dependency scanner

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