CVE-2024-21281
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 Banking Liquidity Management product of Oracle Financial Services Applications (component: Infrastructure). The supported version that is affected is 14.7.0.6.0. Difficult to exploit vulnerability allows high 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 unauthorized creation, deletion or modification access to critical data or all Oracle Banking Liquidity Management accessible data as well as unauthorized read access to a subset of Oracle Banking Liquidity Management accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Banking Liquidity Management. CVSS 3.1 Base Score 5.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:L).
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 Banking Liquidity Management's Infrastructure component (version 14.7.0.6.0). Exploitation requires a high-privileged attacker with network access via HTTP and human interaction from a separate user. The attack vector has high complexity (AC:H), requiring user interaction (UI:R) and high privileges (PR:H). Successful exploitation allows unauthorized creation, deletion, or modification of critical data (high integrity impact) and read access to a subset of data (low confidentiality), plus partial denial of service.
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= 14.7.0.6.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
- High
- Privileges
- High
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:L
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.
-
Locate Oracle Banking Liquidity Management installationIdentify the installation directory or Oracle inventory where Oracle Banking Liquidity Management is installed. Common locations include $ORACLE_HOME or dedicated application directories. Use Oracle Universal Installer (OUI) or check with your system administrator for the installation path.Affected if The product is installed and the version cannot be determined or is not documented.
-
Retrieve the installed versionRun the Oracle inventory command 'opatch lsinventory' or check the product's about/version information through Oracle Enterprise Manager, or inspect version files in the installation directory. Look for the exact version string of the Infrastructure component.Affected if The installed version is 14.7.0.6.0 exactly.
-
Verify the Infrastructure component versionCheck the specific version of the Infrastructure component within Oracle Banking Liquidity Management. This can be done via Oracle Opatch, the Oracle OUI inventory, or the product's component listing. Confirm that the Infrastructure component reports version 14.7.0.6.0.Affected if The Infrastructure component version matches 14.7.0.6.0.
-
Confirm network exposure and privilege modelReview the network accessibility of the affected system (via HTTP/HTTPS endpoints) and verify if high-privileged user accounts exist with network access. Check access control configurations to determine if high-privileged attackers could reach the Infrastructure component over the network.Affected if The system is network-accessible via HTTP and high-privileged user accounts have network access, making exploitation feasible.
A system is affected if Oracle Banking Liquidity Management with Infrastructure component version 14.7.0.6.0 is installed and network-accessible to high-privileged users.
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 (CPU) that addresses this vulnerability. Given the high integrity impact and requirement for high privileges, prioritize patching for systems handling critical financial data. Implement strict least-privilege access controls and user awareness training to mitigate the human interaction requirement.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-21281 — 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-2024-21281 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