Retail Price Management vulnerabilitiesAnd the versions its exploited flaws hit.
Retail Price Management is made by Oracle. We track 6 published vulnerabilities in it, across 17 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 Price Management, check your version against the exploited flaws below and patch those first.
The most recent Retail Price Management flaw added to the known-exploited list is CVE-2017-12617, on 25 March 2022. We keep watching the known-exploited list.
Which versions of Retail Price 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-2017-12617Exploited list, 25 Mar 2022
Apache Tomcat Remote Code Execution Vulnerability
12.013.013.113.214.014.115.016.0
Which Retail Price 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.
- 8.1Apache 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.
Which Retail Price 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.
- >99%CVE-2021-45105Medium
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.
- >99%
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.
- 28%CVE-2019-10086High
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.
- 7.3%CVE-2020-10683Critical
dom4j before 2.0.3 and 2.1.x before 2.1.3 allows external DTDs and External Entities by default, which might enable XXE attacks.
- 2.4%CVE-2021-2351High
Vulnerability in the Advanced Networking Option component of Oracle Database Server.
- 2.2%CVE-2019-10219Medium
A vulnerability was found in Hibernate-Validator.
Running Retail Price 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.
- 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
When running Apache Tomcat, it is possible to upload a JSP file to the server via a specially crafted request. This JSP could then be requested and any code it contained would be executed by the server.
- Matched to
- Retail Price Management 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 6 published vulnerabilities listed under the name Retail Price Management, across 17 versions. The most recent Retail Price 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.
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 Price 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.