Search for packages
| purl | pkg:rpm/redhat/jboss-as-threads@7.5.24-2.Final_redhat_00001.1.ep6?arch=el6 |
| Next non-vulnerable version | None. |
| Latest non-vulnerable version | None. |
| Risk | 10.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1vfk-arae-ubha
Aliases: CVE-2022-23302 GHSA-w9p3-5cr8-m3jj |
Deserialization of Untrusted Data in Log4j 1.x JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, 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. | There are no reported fixed by versions. |
|
VCID-698m-2hju-2qcv
Aliases: CVE-2021-4104 GHSA-fp5r-v3w9-4333 |
Deserialization of Untrusted Data JMSAppender in Log4j 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 when specifically configured to use JMSAppender, which is not the default. Apache Log4j reached end of life in August Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. | There are no reported fixed by versions. |
|
VCID-9k99-jzq8-fyge
Aliases: CVE-2022-23305 GHSA-65fg-84f6-3jq3 |
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') By design, the JDBCAppender in Log4j accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j when specifically configured to use the JDBCAppender, which is not the default. Beginning, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j reached end of life in August Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions. | There are no reported fixed by versions. |
|
VCID-bbq3-tx7c-yucn
Aliases: CVE-2022-23307 GHSA-f7vh-qwp3-x37m |
This advisory has been marked as False Positive and removed. | There are no reported fixed by versions. |
|
VCID-h1pw-28zg-mkae
Aliases: CVE-2020-14384 |
jbossweb: Incomplete fix of CVE-2020-13935 for WebSocket in JBossWeb could lead to DoS | There are no reported fixed by versions. |
|
VCID-nvbx-q971-skgm
Aliases: CVE-2020-13935 GHSA-m7jv-hq7h-mq7c |
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service. | There are no reported fixed by versions. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||