dbcve.org
Financial Services Liquidity Risk ManagementApplication · Oracle

CVE-2020-2891

HIGH · 7.1 CVSS v3.1 Published 2020-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
Remotely reachable 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 Liquidity Risk Management product of Oracle Financial Services Applications (component: User Interfaces). The supported version that is affected is 8.0.6. Easily exploitable vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Financial Services Liquidity Risk Management. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Financial Services Liquidity Risk Management accessible data as well as unauthorized read access to a subset of Oracle Financial Services Liquidity Risk Management accessible data. CVSS 3.0 Base Score 7.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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

Broken access control vulnerability in the User Interfaces component of Oracle Financial Services Liquidity Risk Management v8.0.6. Allows low-privileged attackers with network access via HTTP to perform unauthorized create, delete, and modify operations on critical data (high integrity impact) as well as unauthorized read access to a subset of accessible data (low confidentiality impact). Likely an Insecure Direct Object Reference (IDOR) or insufficient authorization check in UI-to-backend request handling.

MitigationApply Oracle Critical Patch Update (CPU) for January 2021 or subsequent patch addressing CVE-2020-2891. As an interim control, restrict network access to the application to trusted IPs and implement WAF rules to detect abnormal parameter tampering in user interface requests.

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 Liquidity Risk ManagementApplication
Affected:= 8.0.6

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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 the installed version of Oracle Financial Services Liquidity Risk Management
    Locate the product installation directory and check version files, or query the application using administrative console or system information endpoints typically found in Oracle Financial Services applications (often in configuration or about pages).
    Affected if The installed version is exactly 8.0.6
  2. Confirm the User Interfaces component is enabled
    Check the application configuration or deployment settings to verify if the UI component is deployed and active. This may be in the application server configuration (WebLogic, etc.) or in the application's module settings.
    Affected if The UI component is deployed and accessible to users
  3. Verify network accessibility of the application HTTP interface
    Attempt to access the application's HTTP endpoints from a network perspective, or review firewall and network configuration to determine if the UI is exposed to untrusted networks.
    Affected if The application UI is reachable over HTTP from untrusted networks
  4. Check for presence of authorization controls on UI request handling
    Review application logs or proxy configurations for abnormal parameter patterns in UI-to-backend requests. Examine if the application implements consistent authorization checks on all API endpoints serving UI operations.
    Affected if No explicit authorization validation is performed on UI-triggered operations or if IDOR patterns are detectable in request handling

You are affected if Oracle Financial Services Liquidity Risk Management version 8.0.6 is installed with the User Interfaces component exposed to network access and lacking proper authorization controls on create, delete, modify, and read operations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Update (CPU) for January 2021 or subsequent patch addressing CVE-2020-2891. As an interim control, restrict network access to the application to trusted IPs and implement WAF rules to detect abnormal parameter tampering in user interface requests.

Fix this in Financial Services Liquidity Risk Management 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 help mitigating

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-2891 — 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-2891 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