Retail Returns Management vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited6 versions
The short answer

Retail Returns Management is made by Oracle. We track 21 published vulnerabilities in it, across 6 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 Returns Management, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Retail Returns Management 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 Returns Management do the exploited flaws hit?

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

Known exploited

Which Retail Returns 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.

  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 Returns 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%

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

    In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e.

    CVSS6.1Published29 Apr 2020
  4. 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
  5. 87%

    jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution.

    CVSS6.1Published20 Apr 2019
  6. 77%

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through...

    CVSS9.8Published6 Apr 2018
  7. 34%

    Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to configure Spring MVC to serve static resources (e.g.

    CVSS5.9Published6 Apr 2018
  8. 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
  9. 19%

    In Apache Batik 1.x before 1.10, when deserializing subclass of `AbstractDocument`, the class takes a string from the inputStream as the class name which then use it to call the no-arg constructor of the class.

    CVSS9.8Published24 May 2018
  10. 17%

    initDocumentParser in xml/XMLSchedulingDataProcessor.java in Terracotta Quartz Scheduler through 2.3.0 allows XXE attacks via a job description.

    CVSS9.8Published26 Jul 2019
Precursor Intelligence

Running Retail Returns 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 21 published vulnerabilities listed under the name Retail Returns Management, across 6 versions. The most recent Retail Returns Management 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.

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