Jboss Web Server Red Hat Jboss Web Server

Do you want an email whenever new security vulnerabilities are reported in Red Hat Jboss Web Server?

Recent Red Hat Jboss Web Server Security Advisories

Advisory Title Published
RHSA-2022:1520 (RHSA-2022:1520) Important: Red Hat JBoss Web Server 5.6.2 Security Update May 2, 2022
RHSA-2022:1519 (RHSA-2022:1519) Important: Red Hat JBoss Web Server 5.6.2 Security Update May 2, 2022
RHSA-2022:0527 (RHSA-2022:0527) Low: Red Hat JBoss Web Server 3.1 Service Pack 14 security update February 14, 2022
RHSA-2022:0524 (RHSA-2022:0524) Low: Red Hat JBoss Web Server 3.1 Service Pack 14 Security Update February 14, 2022
RHSA-2021:4863 (RHSA-2021:4863) Important: Red Hat JBoss Web Server 5.6.0 Security release November 30, 2021
RHSA-2021:4861 (RHSA-2021:4861) Important: Red Hat JBoss Web Server 5.6.0 Security release November 30, 2021
RHSA-2021:3743 (RHSA-2021:3743) Important: Red Hat JBoss Web Server 5.5.1 Security Update October 6, 2021
RHSA-2021:3741 (RHSA-2021:3741) Important: Red Hat JBoss Web Server 5.5.1 Security Update October 6, 2021
RHSA-2021:2561 (RHSA-2021:2561) Moderate: Red Hat JBoss Web Server 5.5.0 Security release June 29, 2021
RHSA-2021:2562 (RHSA-2021:2562) Moderate: Red Hat JBoss Web Server 5.5.0 security release June 29, 2021

By the Year

In 2022 there have been 0 vulnerabilities in Red Hat Jboss Web Server . Last year Jboss Web Server had 1 security vulnerability published. Right now, Jboss Web Server is on track to have less security vulnerabilities in 2022 than it did last year.

Year Vulnerabilities Average Score
2022 0 0.00
2021 1 7.50
2020 0 0.00
2019 0 0.00
2018 0 0.00

It may take a day or so for new Jboss Web Server vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.

Recent Red Hat Jboss Web Server Security Vulnerabilities

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration

CVE-2021-4104 7.5 - High - December 14, 2021

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Marshaling, Unmarshaling

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data

CVE-2016-2183 7.5 - High - September 01, 2016

The DES and Triple DES ciphers, as used in the TLS, SSH, and IPSec protocols and other protocols and products, have a birthday bound of approximately four billion blocks, which makes it easier for remote attackers to obtain cleartext data via a birthday attack against a long-duration encrypted session, as demonstrated by an HTTPS session using Triple DES in CBC mode, aka a "Sweet32" attack.

Information Disclosure

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Red Hat Enterprise Linux (RHEL) or by Red Hat? Click the Watch button to subscribe.

Red Hat
Vendor

subscribe