Resteasy CVEs
25 CVEs, 6 protected by Waratek
Overview 25 matches · 6 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
6
24.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
19
76.0%
blocked by ARMR today
6
24.0%
partly blocked
0
0.0%
not blocked
19
76.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
25
100.0%
split by
peak 5 / year
20122
Protected by Waratek2
Medium2
blocked by ARMR today2
No public exploit2
20130
20142
Protected by Waratek2
High1
Medium1
blocked by ARMR today2
No public exploit2
20150
20162
No exploit published2
High1
Medium1
not blocked2
No public exploit2
20173
No exploit published3
High1
Medium2
not blocked3
No public exploit3
20182
Protected by Waratek1
No exploit published1
High2
blocked by ARMR today1
not blocked1
No public exploit2
20190
20202
No exploit published2
High1
Medium1
not blocked2
No public exploit2
20215
No exploit published5
High1
Medium4
not blocked5
No public exploit5
20220
20232
No exploit published2
Medium1
Low1
not blocked2
No public exploit2
20244
Protected by Waratek1
No exploit published3
Critical1
Medium3
blocked by ARMR today1
not blocked3
No public exploit4
20251
No exploit published1
High1
not blocked1
No public exploit1
2013201520172019202120232025
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2025-1634 | High | 2025-02-26 | No exploit published | No public exploit | A flaw was found in the quarkus-resteasy extension, which causes memory leaks when client requests with low timeouts are made. If a client request times out, a buffer is not released correctly, leading to increased memory usage and eventual application crash due to OutOfMemoryError. |
| CVE-2024-9622 | Medium | 2024-10-08 | No exploit published | No public exploit | A vulnerability was found in the resteasy-netty4 library arising from improper handling of HTTP requests using smuggling techniques. When an HTTP smuggling request with an ASCII control character is sent, it causes the Netty HttpObjectDecoder to transition into a BAD_MESSAGE state. As a result, any subsequent legitimate requests on the same connection are ignored, leading to client timeouts, which may impact systems using load balancers and expose them to risk. |
| CVE-2024-1726 | Medium | 2024-04-25 | No exploit published | No public exploit | A flaw was discovered in the RESTEasy Reactive implementation in Quarkus. Due to security checks for some JAX-RS endpoints being performed after serialization, more processing resources are consumed while the HTTP request is checked. In certain configurations, if an attacker has knowledge of any POST, PUT, or PATCH request paths, they can potentially identify vulnerable endpoints and trigger excessive resource usage as the endpoints process the requests. This can result in a denial of service. |
| CVE-2023-5675 | Medium | 2024-04-25 | No exploit published | No public exploit | A flaw was found in Quarkus. When a Quarkus RestEasy Classic or Reactive JAX-RS endpoint has its methods declared in the abstract Java class or customized by Quarkus extensions using the annotation processor, the authorization of these methods will not be enforced if it is enabled by either 'quarkus.security.jaxrs.deny-unannotated-endpoints' or 'quarkus.security.jaxrs.default-roles-allowed' properties. |
| CVE-2023-6267 | Critical | 2024-01-25 | Protected by Waratek | No public exploit | A flaw was found in the json payload. If annotation based security is used to secure a REST resource, the JSON body that the resource may consume is being processed (deserialized) prior to the security constraints being evaluated and applied. This does not happen with configuration based security. |
| CVE-2023-0481 | Low | 2023-02-24 | No exploit published | No public exploit | In RestEasy Reactive implementation of Quarkus the insecure File.createTempFile() is used in the FileBodyHandler class which creates temp files with insecure permissions that could be read by a local user. |
| CVE-2023-0482 | Medium | 2023-02-17 | No exploit published | No public exploit | In RESTEasy the insecure File.createTempFile() is used in the DataSourceProvider, FileProvider and Mime4JWorkaround classes which creates temp files with insecure permissions that could be read by a local user. |
| CVE-2021-20293 | Medium | 2021-06-10 | No exploit published | No public exploit | A reflected Cross-Site Scripting (XSS) flaw was found in RESTEasy in all versions of RESTEasy up to 4.6.0.Final, where it did not properly handle URL encoding when calling @javax.ws.rs.PathParam without any @Produces MediaType. This flaw allows an attacker to launch a reflected XSS attack. The highest threat from this vulnerability is to data confidentiality and integrity. |
| CVE-2020-14326 | High | 2021-06-02 | No exploit published | No public exploit | A vulnerability was found in RESTEasy, where RootNode incorrectly caches routes. This issue results in hash flooding, leading to slower requests with higher CPU time spent searching and adding the entry. This flaw allows an attacker to cause a denial of service. |
| CVE-2020-10688 | Medium | 2021-05-27 | No exploit published | No public exploit | A cross-site scripting (XSS) flaw was found in RESTEasy in versions before 3.11.1.Final and before 4.5.3.Final, where it did not properly handle URL encoding when the RESTEASY003870 exception occurs. An attacker could use this flaw to launch a reflected XSS attack. |
| CVE-2020-25724 | Medium | 2021-05-26 | No exploit published | No public exploit | A flaw was found in RESTEasy, where an incorrect response to an HTTP request is provided. This flaw allows an attacker to gain access to privileged information. The highest threat from this vulnerability is to confidentiality and integrity. Versions before resteasy 2.0.0.Alpha3 are affected. |
| CVE-2021-20289 | Medium | 2021-03-26 | No exploit published | No public exploit | A flaw was found in RESTEasy in all versions of RESTEasy up to 4.6.0.Final. The endpoint class and method names are returned as part of the exception response when RESTEasy cannot convert one of the request URI path or query values to the matching JAX-RS resource method's parameter value. The highest threat from this vulnerability is to data confidentiality. |
| CVE-2020-25633 | Medium | 2020-09-18 | No exploit published | No public exploit | A flaw was found in RESTEasy client in all versions of RESTEasy up to 4.5.6.Final. It may allow client users to obtain the server's potentially sensitive information when the server got WebApplicationException from the RESTEasy client call. The highest threat from this vulnerability is to data confidentiality. |
| CVE-2020-1695 | High | 2020-05-19 | No exploit published | No public exploit | A flaw was found in all resteasy 3.x.x versions prior to 3.12.0.Final and all resteasy 4.x.x versions prior to 4.6.0.Final, where an improper input validation results in returning an illegal header that integrates into the server's response. This flaw may result in an injection, which leads to unexpected behavior when the HTTP response is constructed. |
| CVE-2016-9606 | High | 2018-03-09 | No exploit published | No public exploit | JBoss RESTEasy before version 3.1.2 could be forced into parsing a request with YamlProvider, resulting in unmarshalling of potentially untrusted data which could allow an attacker to execute arbitrary code with RESTEasy application permissions. |
| CVE-2018-1051 | High | 2018-01-25 | Protected by Waratek | No public exploit | It was found that the fix for CVE-2016-9606 in versions 3.0.22 and 3.1.2 was incomplete and Yaml unmarshalling in Resteasy is still possible via `Yaml.load()` in YamlProvider. |
| CVE-2017-7561 | High | 2017-09-13 | No exploit published | No public exploit | Red Hat JBoss EAP version 3.0.7 through before 4.0.0.Beta1 is vulnerable to a server-side cache poisoning or CORS requests in the JAX-RS component resulting in a moderate impact. |
| CVE-2016-6347 | Medium | 2017-04-20 | No exploit published | No public exploit | Cross-site scripting (XSS) vulnerability in the default exception handler in RESTEasy allows remote attackers to inject arbitrary web script or HTML via unspecified vectors. |
| CVE-2016-6348 | Medium | 2017-04-12 | No exploit published | No public exploit | JacksonJsonpInterceptor in RESTEasy might allow remote attackers to conduct a cross-site script inclusion (XSSI) attack. |
| CVE-2016-6346 | High | 2016-09-07 | No exploit published | No public exploit | RESTEasy enables GZIPInterceptor, which allows remote attackers to cause a denial of service via unspecified vectors. |
| CVE-2016-6345 | Medium | 2016-09-07 | No exploit published | No public exploit | RESTEasy allows remote authenticated users to obtain sensitive information by leveraging "insufficient use of random values" in async jobs. |
| CVE-2014-7839 | Medium | 2014-11-25 | Protected by Waratek | No public exploit | DocumentProvider in RESTEasy 2.3.7 and 3.0.9 does not configure the (1) external-general-entities or (2) external-parameter-entities features, which allows remote attackers to conduct XML external entity (XXE) attacks via unspecified vectors. |
| CVE-2014-3490 | High | 2014-08-19 | Protected by Waratek | No public exploit | RESTEasy 2.3.1 before 2.3.8.SP2 and 3.x before 3.0.9, as used in Red Hat JBoss Enterprise Application Platform (EAP) 6.3.0, does not disable external entities when the resteasy.document.expand.entity.references parameter is set to false, which allows remote attackers to read arbitrary files and have other unspecified impact via unspecified vectors, related to an XML External Entity (XXE) issue. NOTE: this vulnerability exists because of an incomplete fix for CVE-2012-0818. |
| CVE-2012-0818 | Medium | 2012-11-23 | Protected by Waratek | No public exploit | RESTEasy before 2.3.1 allows remote attackers to read arbitrary files via an external entity reference in a DOM document, aka an XML external entity (XXE) injection attack. |
| CVE-2011-5245 | Medium | 2012-11-23 | Protected by Waratek | No public exploit | The readFrom function in providers.jaxb.JAXBXmlTypeProvider in RESTEasy before 2.3.2 allows remote attackers to read arbitrary files via an external entity reference in a Java Architecture for XML Binding (JAXB) input, aka an XML external entity (XXE) injection attack, a similar vulnerability to CVE-2012-0818. |