Fuse vulnerabilitiesAnd the versions its exploited flaws hit.
Fuse is made by Red Hat. We track 25 published vulnerabilities in it, across 18 versions. 3 of them are on the list of flaws known to be exploited, the newest added on 25 March 2022. If you run Fuse, check your version against the exploited flaws below and patch those first.
The most recent Fuse flaw added to the known-exploited list is CVE-2015-1427, on 25 March 2022. We keep watching the known-exploited list.
Which versions of Fuse do the exploited flaws hit?
Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.
- CVE-2015-1427Exploited list, 25 Mar 2022
Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability
1.0.0 - CVE-2017-12617Exploited list, 25 Mar 2022
Apache Tomcat Remote Code Execution Vulnerability
1.0 - CVE-2016-4437Exploited list, 3 Nov 2021
Apache Shiro Code Execution Vulnerability
1.0
Which Fuse vulnerabilities are being exploited?
3 flaws are 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.8Elasticsearch Groovy Scripting Engine Remote Code Execution Vulnerability
The Groovy scripting engine in Elasticsearch allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands.
- 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.
- 9.8Apache Shiro Code Execution Vulnerability
Apache Shiro contains a vulnerability which may allow remote attackers to execute code or bypass intended access restrictions via an unspecified request parameter when a cipher key has not been configured for the...
Which Fuse 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%
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.
- >99%
The Groovy scripting engine in Elasticsearch before 1.3.8 and 1.4.x before 1.4.3 allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands via a crafted script.
- 93%
Apache Shiro before 1.2.5, when a cipher key has not been configured for the "remember me" feature, allows remote attackers to execute arbitrary code or bypass intended access restrictions via an unspecified request...
- 90%CVE-2017-5645Critical
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when...
- 77%CVE-2018-1270Critical
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...
- 9.7%CVE-2019-0201Medium
An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta.
- 4.9%CVE-2017-7957High
XStream through 1.4.9, when a certain denyTypes workaround is not used, mishandles attempts to create an instance of the primitive type 'void' during unmarshalling, leading to a remote application crash, as...
- 4.6%CVE-2024-1635High
A vulnerability was found in Undertow. This vulnerability impacts a server that supports the wildfly-http-client protocol.
- 3.1%CVE-2019-10174High
A vulnerability was found in Infinispan such that the invokeAccessibly method from the public class ReflectionUtil allows any application class to invoke private methods in any class with Infinispan's privileges.
- 2.9%CVE-2018-1199Medium
Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing...
Running Fuse? 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
The Groovy scripting engine in Elasticsearch allows remote attackers to bypass the sandbox protection mechanism and execute arbitrary shell commands.
- Matched to
- Fuse 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 25 published vulnerabilities listed under the name Fuse, across 18 versions. The most recent Fuse flaw added to the known-exploited list is CVE-2015-1427, on 25 March 2022.
3 are on the list of flaws known to be exploited. The most recently added are CVE-2015-1427, CVE-2017-12617 and CVE-2016-4437.
Each flaw names its own versions, usually as ranges. The newest, CVE-2015-1427, affects 1.0.0. The versions for every exploited flaw are listed on this page.
Create a Precursor Intelligence account and track Fuse. 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.