dbcve.org
Banking Liquidity ManagementApplication · Oracle

CVE-2024-21284

HIGH · 7.1 CVSS v3.1 Published 2024-10-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

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 Banking Liquidity Management product of Oracle Financial Services Applications (component: Reports). The supported version that is affected is 14.5.0.12.0. Difficult to exploit vulnerability allows low privileged attacker with network access via HTTP to compromise Oracle Banking Liquidity Management. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Banking Liquidity Management. CVSS 3.1 Base Score 7.1 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 · moderate confidence

Vulnerability in the Reports component of Oracle Banking Liquidity Management (v14.5.0.12.0) allows a low-privileged attacker with network access to achieve complete system takeover, but requires human interaction to exploit. The exact vulnerability type (injection, authentication bypass, etc.) is not specified in the advisory.

MitigationApply the Oracle patch for CVE-2024-21284 when available. Until then, restrict network access to the Reports component and implement additional authentication controls for report generation functions.

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
Banking Liquidity ManagementApplication
Affected:= 14.5.0.12.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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/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 Banking Liquidity Management installation
    Locate Oracle Banking Liquidity Management installation directory or check Oracle inventory files (typically in $ORACLE_HOME/oraInventory/ContentsXML/inventory.xml) for entries containing 'Oracle Banking Liquidity Management' or 'liquidity management'
    Affected if The product is not installed on the system
  2. Verify exact version number
    Check the installed version of Oracle Banking Liquidity Management by examining version files in the installation directory, Oracle inventory, or by querying the application's about/version endpoint if available. The affected version is exactly 14.5.0.12.0
    Affected if The installed version is exactly 14.5.0.12.0 (no other version ranges are listed as affected)
  3. Confirm Reports component is accessible
    Check if the Reports component is deployed and accessible. This may be a web endpoint (commonly /reports, /reporter, or similar), a configured report generation service, or a module within the application. Review application configuration files, deployment descriptors, and accessible URLs
    Affected if The Reports component is exposed and reachable on the network (the vulnerability exists specifically in this component)

User is affected if Oracle Banking Liquidity Management version 14.5.0.12.0 is installed AND the Reports component is deployed and network-accessible, as the vulnerability resides specifically in that component and can be exploited by a low-privileged attacker with network access and human interaction.

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 the Oracle patch for CVE-2024-21284 when available. Until then, restrict network access to the Reports component and implement additional authentication controls for report generation functions.

Fix this in Banking Liquidity Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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