WildFly 41.0.1 is released!
WildFly 41.0.1.Final is now available for download.
The full release notes are available in GitHub. The release notes for the WildFly Core 33.0.1.Final release included in WildFly 41.0.1 are also available in GitHub.
A number of the fixes and component upgrades in this release address vulnerabilities, so we would also like to draw the following changes to your attention:
-
WFCORE-7670 — We have added a significant deny-list to our out-of-the-box JEPS 290 global filter (i.e. the filter set at boot via -Djdk.serialFilter.). The filter setting can be seen in the bin/jdk.serialFilter file. If your application needs to deserialize types denied by this filter you may need to edit the exclusions in
bin/jdk.serialFilter. Typical deserialization use cases include handling remote EJB invocations, reading JMS ObjectMessages and serializing and deserializing session content for passivation to disk or a remote Infinispan cluster or for replication using Infinispan. -
This release also includes an updated version of Apache CXF which supports blocking decoupled WS-Addressing destinations as a mitigation to reduce the server side request forgery (SSRF) risk. To preserve backwards compatibility, this blocking is disabled by default but it can be enabled by setting the system property
org.jboss.ws.cxf.decoupledEndpointEnabled=false. -
If the
undertowsubsystem’sajp-listenerresource is configured, theio.undertow.ajp.AJP_SECRETsystem property must be set with a value that must match the value of asecretrequest attribute provided with all AJP requests. Any request that does not provide the expectedsecretattribute value will be receive an HTTP 403 Forbidden response. If theio.undertow.ajp.AJP_SECRETproperty is not set, the listener will fail to start. To disable the requirement to configure a secret and use thesecretrequest attribute, set theio.undertow.ajp.REQUIRE_AJP_SECRETsystem property tofalse. Note that the AJP listener is deprecated. Users should migrate to HTTP proxying which offers all the same functionality as AJP with proper TLS and mutual authentication support. Provide any feedback in the WildFly google group, Zulip or JIRA.
Enjoy!