Integration Camel Quarkus Red Hat Integration Camel Quarkus

Do you want an email whenever new security vulnerabilities are reported in Red Hat Integration Camel Quarkus?

Recent Red Hat Integration Camel Quarkus Security Advisories

Advisory Title Published
RHSA-2021:3207 (RHSA-2021:3207) Moderate: Red Hat Integration Camel Quarkus Tech-Preview 2 security update August 18, 2021

By the Year

In 2022 there have been 0 vulnerabilities in Red Hat Integration Camel Quarkus . Last year Integration Camel Quarkus had 3 security vulnerabilities published. Right now, Integration Camel Quarkus is on track to have less security vulnerabilities in 2022 than it did last year.

Year Vulnerabilities Average Score
2022 0 0.00
2021 3 5.87
2020 0 0.00
2019 0 0.00
2018 0 0.00

It may take a day or so for new Integration Camel Quarkus 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 Integration Camel Quarkus 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

A flaw was found in Wildfly Elytron in versions prior to 1.10.14.Final

CVE-2021-3642 5.3 - Medium - August 05, 2021

A flaw was found in Wildfly Elytron in versions prior to 1.10.14.Final, prior to 1.15.5.Final and prior to 1.16.1.Final where ScramServer may be susceptible to Timing Attack if enabled. The highest threat of this vulnerability is confidentiality.

Side Channel Attack

A flaw was found in Wildfly in versions before 23.0.2.Final while creating a new role in domain mode

CVE-2021-3536 4.8 - Medium - May 20, 2021

A flaw was found in Wildfly in versions before 23.0.2.Final while creating a new role in domain mode via the admin console, it is possible to add a payload in the name field, leading to XSS. This affects Confidentiality and Integrity.

XSS

Stay on top of Security Vulnerabilities

Want an email whenever new vulnerabilities are published for Red Hat Wildfly or by Red Hat? Click the Watch button to subscribe.

Red Hat
Vendor

subscribe