Financial Services Enterprise Case Management vulnerabilitiesAnd the versions its exploited flaws hit.

Product2 known exploited12 versions
The short answer

Financial Services Enterprise Case Management is made by Oracle. We track 11 published vulnerabilities in it, across 12 versions. 2 of them are on the list of flaws known to be exploited, the newest added on 25 August 2022. If you run Financial Services Enterprise Case Management, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Financial Services Enterprise Case Management flaw added to the known-exploited list is CVE-2022-22963, on 25 August 2022. We keep watching the known-exploited list.

Versions

Which versions of Financial Services Enterprise Case 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

    8.1.1.08.1.1.18.1.2.0
  • CVE-2022-22965Exploited list, 4 Apr 2022

    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    8.1.1.08.1.1.18.1.2.0
Known exploited

Which Financial Services Enterprise Case Management vulnerabilities are being exploited?

2 flaws are 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.

  1. 9.8
    CVE-2022-22963CriticalKnown exploited
    VMware 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...

    Chance of use>99%Known exploited since25 Aug 2022
  2. 9.8
    CVE-2022-22965CriticalKnown exploited
    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.

    Chance of use>99%Known exploited since4 Apr 2022
Exploit likelihood

Which Financial Services Enterprise Case 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.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2022-22963CriticalKnown exploited

    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...

    CVSS9.8Published1 Apr 2022
  2. >99%
    CVE-2022-22965CriticalKnown exploited

    A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.

    CVSS9.8Published1 Apr 2022
  3. 13%

    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.

    CVSS7.5Published13 Jul 2021
  4. 12%

    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.

    CVSS7.5Published13 Jul 2021
  5. 12%

    There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads.

    CVSS6.5Published24 Jan 2022
  6. 12%

    When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop.

    CVSS7.5Published13 Jul 2021
  7. 11%

    When reading a specially crafted TAR 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.

    CVSS7.5Published13 Jul 2021
  8. 6.2%

    Some components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful.

    CVSS5.9Published22 Sep 2021
  9. 4.9%

    jackson-databind before 2.13.0 allows a Java StackOverflow exception and denial of service via a large depth of nested objects.

    CVSS7.5Published11 Mar 2022
  10. 2.4%

    Vulnerability in the Advanced Networking Option component of Oracle Database Server.

    CVSS8.3Published21 Jul 2021
Precursor Intelligence

Running Financial Services Enterprise Case 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.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. 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.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 11 published vulnerabilities listed under the name Financial Services Enterprise Case Management, across 12 versions. The most recent Financial Services Enterprise Case Management flaw added to the known-exploited list is CVE-2022-22963, on 25 August 2022.

2 are on the list of flaws known to be exploited. The most recently added are CVE-2022-22963 and CVE-2022-22965.

Each flaw names its own versions, usually as ranges. The newest, CVE-2022-22963, affects 8.1.1.0, 8.1.1.1, 8.1.2.0. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Financial Services Enterprise Case 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.