CVE-2020-14691
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 · uneditedVulnerability in the Oracle Financial Services Liquidity Risk Management product of Oracle Financial Services Applications (component: User Interface). 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.1 Base Score 7.1 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/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 confidenceVulnerability in Oracle Financial Services Liquidity Risk Management User Interface component (v8.0.6) allows low-privileged attackers with network access via HTTP to perform unauthorized create, delete, or modify operations on critical data, plus read access to a subset of data. The CVSS vector indicates low attack complexity and no user interaction required, with high integrity impact.
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= 8.0.6.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed LRM versionQuery the Oracle Financial Services Liquidity Risk Management application for its version number. This is typically found in the application About section, in the installation directory metadata, or via the Oracle Financial Services LRM administrative console under the version or system information panel.Affected if The installed version is exactly 8.0.6.0.0 (the affected version listed in the CVE)
-
Confirm LRM User Interface is enabledVerify that the Liquidity Risk Management User Interface component is deployed and accessible. Check the application server (WebLogic, etc.) deployment status for the LRM UI application or web module.Affected if The LRM UI component is deployed and running, making the HTTP attack vector viable
-
Verify network accessibility of LRM UIDetermine if the LRM User Interface is exposed over HTTP/HTTPS to the network. Check the application server listener configurations, load balancer rules, or firewall policies that permit HTTP access to the LRM UI endpoint.Affected if The LRM UI is reachable via network HTTP/HTTPS, enabling the network attack vector described in the CVSS
-
Audit low-privileged user accountsReview the Oracle Financial Services LRM user directory or database for accounts with low-privilege roles. Identify which users have basic or standard access levels versus administrative or elevated privileges.Affected if Low-privileged user accounts exist in the system; these accounts could potentially exploit the vulnerability to perform unauthorized create, delete, or modify operations
-
Check authorization enforcement on UI actionsInspect the LRM UI and backend API authorization configurations to determine whether create, delete, and modify operations are properly restricted based on user privilege levels. Review role-based access control (RBAC) policies or permission matrices for the LRM application.Affected if Authorization controls are missing, weak, or misconfigured, allowing low-privileged users to perform high-integrity operations
A user is affected if they have Oracle Financial Services Liquidity Risk Management version 8.0.6.0.0 deployed with the User Interface component accessible over the network, and low-privileged user accounts exist in the environment.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Oracle Critical Patch Update that addresses CVE-2020-14691; if no patch is available, implement or enforce proper authorization controls at the UI and API layers to ensure low-privileged users cannot access or modify data outside their authorized scope.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14691 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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