Retail Invoice Matching vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited10 versions
The short answer

Retail Invoice Matching is made by Oracle. We track 12 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 March 2022. If you run Retail Invoice Matching, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Retail Invoice Matching flaw added to the known-exploited list is CVE-2017-12617, on 25 March 2022. We keep watching the known-exploited list.

Versions

Which versions of Retail Invoice Matching do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

  • CVE-2017-12617Exploited list, 25 Mar 2022

    Apache Tomcat Remote Code Execution Vulnerability

    12.013.013.113.214.014.115.016.0
Known exploited

Which Retail Invoice Matching 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. 8.1
    CVE-2017-12617HighKnown exploited
    Apache Tomcat Remote Code Execution Vulnerability

    When running Apache Tomcat, it is possible to upload a JSP file to the server via a specially crafted request.

    Chance of use>99%Known exploited since25 Mar 2022
Exploit likelihood

Which Retail Invoice Matching 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-2017-12617HighKnown exploited

    When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.

    CVSS8.1Published4 Oct 2017
  3. 30%

    jQuery before 3.0.0 is vulnerable to Cross-site Scripting (XSS) attacks when a cross-domain Ajax request is performed without the dataType option, causing text/javascript responses to be executed.

    CVSS6.1Published18 Jan 2018
  4. 28%

    In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for an attacker to access the classloader via the class property available on all Java objects.

    CVSS7.3Published20 Aug 2019
  5. 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
  6. 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
  7. 2.6%

    When reading a specially crafted ZIP archive, or a derived formats, an Apache Ant build can be made to allocate large amounts of memory that leads to an out of memory error, even for small inputs.

    CVSS5.5Published14 Jul 2021
  8. 2.5%

    When reading a specially crafted TAR archive an Apache Ant build can be made to allocate large amounts of memory that finally leads to an out of memory error, even for small inputs.

    CVSS5.5Published14 Jul 2021
  9. 2.5%

    faces/context/PartialViewContextImpl.java in Eclipse Mojarra, as used in Mojarra for Eclipse EE4J before 2.3.10 and Mojarra JavaServer Faces before 2.2.20, allows Reflected XSS because a client window field is...

    CVSS6.1Published2 Oct 2019
  10. 2.2%

    A vulnerability was found in Hibernate-Validator.

    CVSS6.1Published8 Nov 2019
Precursor Intelligence

Running Retail Invoice Matching? 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 12 published vulnerabilities listed under the name Retail Invoice Matching, across 10 versions. The most recent Retail Invoice Matching flaw added to the known-exploited list is CVE-2017-12617, on 25 March 2022.

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

Each flaw names its own versions, usually as ranges. The newest, CVE-2017-12617, affects 12.0, 13.0, 13.1, 13.2 and more. The versions for every exploited flaw are listed on this page.

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