RHSA-2025:1637: Important: Red Hat JBoss Enterprise Application Platform 7.4.21 security update
First published: Tue Feb 18 2025(Updated: )
Important: Red Hat JBoss Enterprise Application Platform 7.4.21 security update
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/eap7-hal-console | <3.3.25-1.Final_redhat_00001.1.el8ea | 3.3.25-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-hibernate | <5.3.37-1.Final_redhat_00001.1.el8ea | 5.3.37-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-jbossws-common | <3.4.0-1.Final_redhat_00001.1.el8ea | 3.4.0-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-jbossws-cxf | <5.4.14-1.Final_redhat_00001.1.el8ea | 5.4.14-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-opensaml | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-wildfly | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| redhat/eap7-xml-security | <2.3.5-1.redhat_00001.1.el8ea | 2.3.5-1.redhat_00001.1.el8ea |
| redhat/eap7-hibernate-core | <5.3.37-1.Final_redhat_00001.1.el8ea | 5.3.37-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-hibernate-entitymanager | <5.3.37-1.Final_redhat_00001.1.el8ea | 5.3.37-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-hibernate-envers | <5.3.37-1.Final_redhat_00001.1.el8ea | 5.3.37-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-hibernate-java8 | <5.3.37-1.Final_redhat_00001.1.el8ea | 5.3.37-1.Final_redhat_00001.1.el8ea |
| redhat/eap7-opensaml-core | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-profile-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-saml-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-saml-impl | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-security-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-security-impl | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-soap-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xacml-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xacml-impl | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xacml-saml-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xacml-saml-impl | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xmlsec-api | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-opensaml-xmlsec-impl | <3.4.6-1.redhat_00001.1.el8ea | 3.4.6-1.redhat_00001.1.el8ea |
| redhat/eap7-wildfly-java-jdk11 | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| redhat/eap7-wildfly-java-jdk17 | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| redhat/eap7-wildfly-java-jdk8 | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| redhat/eap7-wildfly-javadocs | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| redhat/eap7-wildfly-modules | <7.4.21-2.GA_redhat_00001.1.el8ea | 7.4.21-2.GA_redhat_00001.1.el8ea |
| JBoss Enterprise Application Platform |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of RHSA-2025:1637?
RHSA-2025:1637 is classified as an Important security update.
How do I fix RHSA-2025:1637?
To fix RHSA-2025:1637, update your Red Hat JBoss Enterprise Application Platform to the specified remedial versions.
Which software is affected by RHSA-2025:1637?
RHSA-2025:1637 affects Red Hat JBoss Enterprise Application Platform 7.4.21 and related packages.
What versions should I upgrade to for RHSA-2025:1637?
You should upgrade to specific versions such as 3.3.25-1.Final_redhat_00001.1.el8ea for eap7-hal-console and others as listed in the advisory.
Is there a need to restart services after applying the fix for RHSA-2025:1637?
Yes, it is generally recommended to restart the services after applying the fix to ensure they run the updated code.
- agent/remedy
- agent/title
- agent/references
- agent/severity
- agent/source
- agent/last-modified-date
- agent/description
- agent/type
- agent/first-publish-date
- collector/redhat-errata-latest
- source/Red Hat
- anchor-id/RHSA-2025:1637
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/event
- agent/tags
- agent/softwarecombine
- collector/redhat-errata
- vendor/red hat
- canonical/jboss enterprise application platform
- package-manager/redhat