Retail Financial Integration vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited15 versions
The short answer

Retail Financial Integration is made by Oracle. We track 19 published vulnerabilities in it, across 15 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 4 April 2022. If you run Retail Financial Integration, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Retail Financial Integration flaw added to the known-exploited list is CVE-2022-22965, on 4 April 2022. We keep watching the known-exploited list.

Versions

Which versions of Retail Financial Integration 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-22965Exploited list, 4 Apr 2022

    Spring Framework JDK 9+ Remote Code Execution Vulnerability

    14.1.3.215.0.3.116.0.319.0.1
Known exploited

Which Retail Financial Integration 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.

  1. 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 Retail Financial Integration 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%

    Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups.

    CVSS5.9Published18 Dec 2021
  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. 89%

    In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a...

    CVSS7.5Published17 Jan 2020
  4. 12%

    The fix for bug 63362 present in Apache Tomcat 10.1.0-M1 to 10.1.0-M5, 10.0.0-M1 to 10.0.11, 9.0.40 to 9.0.53 and 8.5.60 to 8.5.71 introduced a memory leak.

    CVSS7.5Published14 Oct 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%

    In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the...

    CVSS6.5Published19 Sep 2020
  7. 9.2%

    Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources...

    CVSS7.5Published18 Oct 2018
  8. 8.0%

    As mitigation for CVE-2020-1945 Apache Ant 1.10.8 changed the permissions of temporary files it created so that only the current user was allowed to access them.

    CVSS7.5Published1 Oct 2020
  9. 7.4%

    All versions of Apache Santuario - XML Security for Java prior to 2.2.3 and 2.1.7 are vulnerable to an issue where the "secureValidation" property is not passed correctly when creating a KeyInfo from a...

    CVSS7.5Published19 Sep 2021
  10. 2.7%

    Spring Framework (versions 5.0.x prior to 5.0.7, versions 4.3.x prior to 4.3.18, and older unsupported versions) allow web applications to change the HTTP request method to any HTTP method (including TRACE) using the...

    CVSS5.9Published25 Jun 2018
Precursor Intelligence

Running Retail Financial Integration? 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 19 published vulnerabilities listed under the name Retail Financial Integration, across 15 versions. The most recent Retail Financial Integration flaw added to the known-exploited list is CVE-2022-22965, on 4 April 2022.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2022-22965.

Each flaw names its own versions, usually as ranges. The newest, CVE-2022-22965, affects 14.1.3.2, 15.0.3.1, 16.0.3, 19.0.1. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Retail Financial Integration. 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.