Financial Services Crime and Compliance Management Studio vulnerabilitiesAnd the versions its exploited flaws hit.
Financial Services Crime and Compliance Management Studio is made by Oracle. We track 22 published vulnerabilities in it, across 2 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Financial Services Crime and Compliance Management Studio, check your version against the exploited flaws below and patch those first.
The most recent Financial Services Crime and Compliance Management Studio flaw added to the known-exploited list is CVE-2018-1273, on 25 March 2022. We keep watching the known-exploited list.
Which versions of Financial Services Crime and Compliance Management Studio do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2018-1273Exploited list, 25 Mar 2022
VMware Tanzu Spring Data Commons Property Binder Vulnerability
8.0.8.2.08.0.8.3.0
Which Financial Services Crime and Compliance Management Studio 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 Data Commons Property Binder Vulnerability
Spring Data Commons contains a property binder vulnerability which can allow an attacker to perform remote code execution.
Which Financial Services Crime and Compliance Management Studio 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%CVE-2021-34429Medium
For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the content of the WEB-INF directory and/or bypass some security constraints.
- 97%
Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements.
- 76%CVE-2021-41303Critical
Apache Shiro before 1.8.0, when using Apache Shiro with Spring Boot, a specially crafted HTTP request may cause an authentication bypass.
- 21%CVE-2021-23337High
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
- 13%CVE-2021-36090High
When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 12%CVE-2021-35516High
When reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs.
- 12%CVE-2022-22978Critical
In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers.
- 12%CVE-2022-25647High
The package com.google.code.gson:gson before 2.8.9 are vulnerable to Deserialization of Untrusted Data via the writeReplace() method in internal classes, which may lead to DoS attacks.
- 12%CVE-2022-23437Medium
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads.
- 12%CVE-2021-35515High
When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop.
Running Financial Services Crime and Compliance Management Studio? 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
Spring Data Commons contains a property binder vulnerability which can allow an attacker to perform remote code execution.
- Matched to
- Financial Services Crime and Compliance Management Studio 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 22 published vulnerabilities listed under the name Financial Services Crime and Compliance Management Studio, across 2 versions. The most recent Financial Services Crime and Compliance Management Studio flaw added to the known-exploited list is CVE-2018-1273, on 25 March 2022.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2018-1273.
Each flaw names its own versions, usually as ranges. The newest, CVE-2018-1273, affects 8.0.8.2.0, 8.0.8.3.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Financial Services Crime and Compliance Management Studio. 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.