Micros Relate CRM Software vulnerabilitiesAnd the versions its exploited flaws hit.
Micros Relate CRM Software is made by Oracle. We track 4 published vulnerabilities in it, across 2 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 12 May 2023. If you run Micros Relate CRM Software, check your version against the exploited flaws below and patch those first.
The most recent Micros Relate CRM Software flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023. We keep watching the known-exploited list.
Which versions of Micros Relate CRM Software do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2016-8735Exploited list, 12 May 2023
Apache Tomcat Remote Code Execution Vulnerability
10.811.4
Which Micros Relate CRM Software 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.
- 9.8Apache Tomcat Remote Code Execution Vulnerability
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports.
Which Micros Relate CRM Software 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.
- 17%CVE-2018-1304Medium
The URL pattern of "" (the empty string) which exactly maps to the context root was not correctly handled in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 when used as part...
- 14%CVE-2018-1305Medium
Security constraints defined by annotations of Servlets in Apache Tomcat 9.0.0.M1 to 9.0.4, 8.5.0 to 8.5.27, 8.0.0.RC1 to 8.0.49 and 7.0.0 to 7.0.84 were only applied once a Servlet had been loaded.
- 11%CVE-2019-17563High
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack.
Running Micros Relate CRM Software? 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
Apache Tomcat contains an unspecified vulnerability that allows for remote code execution if JmxRemoteLifecycleListener is used and an attacker can reach Java Management Extension (JMX) ports. This CVE exists because this listener wasn't updated for consistency with the Oracle patched issues for CVE-2016-3427 which affected credential types.
- Matched to
- Micros Relate CRM Software 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 4 published vulnerabilities listed under the name Micros Relate CRM Software, across 2 versions. The most recent Micros Relate CRM Software flaw added to the known-exploited list is CVE-2016-8735, on 12 May 2023.
1 is on the list of flaws known to be exploited. The most recently added is CVE-2016-8735.
Each flaw names its own versions, usually as ranges. The newest, CVE-2016-8735, affects 10.8, 11.4. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Micros Relate CRM Software. 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.