Banking Liquidity Management vulnerabilitiesAnd the versions its exploited flaws hit.
Banking Liquidity Management is made by Oracle. We track 9 published vulnerabilities in it, across 10 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 August 2022. If you run Banking Liquidity Management, check your version against the exploited flaws below and patch those first.
The most recent Banking Liquidity Management flaw added to the known-exploited list is CVE-2022-22963, on 25 August 2022. We keep watching the known-exploited list.
Which versions of Banking Liquidity Management do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2022-22963Exploited list, 25 Aug 2022
VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability
14.214.5
Which Banking Liquidity Management vulnerabilities are being exploited?
1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.
- 9.8VMware Tanzu Spring Cloud Function Remote Code Execution Vulnerability
When using routing functionality in VMware Tanzu's Spring Cloud Function, it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to...
Which Banking Liquidity Management flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- >99%
In Spring Cloud Function versions 3.1.6, 3.2.2 and older unsupported versions, when using routing functionality it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in...
- 7.6%CVE-2020-24616High
FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to br.com.anteros.dbcp.AnterosDBCPDataSource (aka Anteros-DBCP).
- 7.3%CVE-2020-24750High
FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.
- 5.2%CVE-2020-8203High
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
- 3.9%CVE-2019-12399High
When Connect workers in Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, or 2.3.0 are configured with one or more config providers, and a connector is created/updated on that Connect cluster to use an...
- 1.8%CVE-2020-1945Medium
Apache Ant 1.1 to 1.9.14 and 1.10.0 to 1.10.7 uses the default temporary directory identified by the Java system property java.io.tmpdir for several tasks and may thus leak sensitive information.
- 0.4%CVE-2024-21284High
Vulnerability in the Oracle Banking Liquidity Management product of Oracle Financial Services Applications (component: Reports).
- 0.4%CVE-2024-21285High
Vulnerability in the Oracle Banking Liquidity Management product of Oracle Financial Services Applications (component: Reports).
- 0.3%CVE-2024-21281Medium
Vulnerability in the Oracle Banking Liquidity Management product of Oracle Financial Services Applications (component: Infrastructure).
Running Banking Liquidity Management? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 flaw being exploited affects software Acme tracks
When using routing functionality in VMware Tanzu's Spring Cloud Function, it is possible for a user to provide a specially crafted SpEL as a routing-expression that may result in remote code execution and access to local resources.
- Matched to
- Banking Liquidity Management on Acme's software list
- What to do
- Patch first, then check for signs of use
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 9 published vulnerabilities listed under the name Banking Liquidity Management, across 10 versions. The most recent Banking Liquidity Management flaw added to the known-exploited list is CVE-2022-22963, on 25 August 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2022-22963.
Each flaw names its own versions, usually as ranges. The newest, CVE-2022-22963, affects 14.2, 14.5. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Banking Liquidity Management. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.