Staging Environment: Content and features may be unstable or change without notice.
Search for packages
Package details: pkg:rpm/redhat/jbossas-modules-eap@7.5.17-1.Final_redhat_4.1.ep6?arch=el6
purl pkg:rpm/redhat/jbossas-modules-eap@7.5.17-1.Final_redhat_4.1.ep6?arch=el6
Next non-vulnerable version None.
Latest non-vulnerable version None.
Risk 10.0
Vulnerabilities affecting this package (3)
Vulnerability Summary Fixed by
VCID-74dr-6hxt-tbgu
Aliases:
CVE-2017-5645
GHSA-fxph-q3j8-mv87
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 deserialized, can execute arbitrary code. There are no reported fixed by versions.
VCID-fyfz-6tr5-2fc7
Aliases:
CVE-2017-5664
GHSA-jmvv-524f-hj5j
The error page mechanism of the Java Servlet Specification requires that, when an error occurs and an error page is configured for the error that occurred, the original request and response are forwarded to the error page. This means that the request is presented to the error page with the original HTTP method. If the error page is a static file, expected behaviour is to serve content of the file as if processing a GET request, regardless of the actual HTTP method. The Default Servlet in Apache Tomcat 9.0.0.M1 to 9.0.0.M20, 8.5.0 to 8.5.14, 8.0.0.RC1 to 8.0.43 and 7.0.0 to 7.0.77 did not do this. Depending on the original request this could lead to unexpected and undesirable results for static error pages including, if the DefaultServlet is configured to permit writes, the replacement or removal of the custom error page. Notes for other user provided error pages: (1) Unless explicitly coded otherwise, JSPs ignore the HTTP method. JSPs used as error pages must must ensure that they handle any error dispatch as a GET request, regardless of the actual method. (2) By default, the response generated by a Servlet does depend on the HTTP method. Custom Servlets used as error pages must ensure that they handle any error dispatch as a GET request, regardless of the actual method. There are no reported fixed by versions.
VCID-v84e-sf92-dqa1
Aliases:
CVE-2017-7525
GHSA-qxxx-2pp7-5hmx
A deserialization flaw was discovered in the jackson-databind, versions before 2.6.7.1, 2.7.9.1 and 2.8.9, which could allow an unauthenticated user to perform code execution by sending the maliciously crafted input to the readValue method of the ObjectMapper. There are no reported fixed by versions.
Vulnerabilities fixed by this package (0)
Vulnerability Summary Aliases
This package is not known to fix vulnerabilities.

Date Actor Action Vulnerability Source VulnerableCode Version
2026-04-01T14:31:27.786502+00:00 RedHat Importer Affected by VCID-74dr-6hxt-tbgu https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2017-5645.json 38.0.0
2026-04-01T14:30:49.307487+00:00 RedHat Importer Affected by VCID-fyfz-6tr5-2fc7 https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2017-5664.json 38.0.0
2026-04-01T14:29:39.067115+00:00 RedHat Importer Affected by VCID-v84e-sf92-dqa1 https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2017-7525.json 38.0.0