https://bugzilla.redhat.com/show_bug.cgi?id=2030932
Andre Costa <andcosta(a)redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(mmccune(a)redhat.co |
|m) |
|needinfo?(security-response |
|-team(a)redhat.com) |
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2030932
https://bugzilla.redhat.com/show_bug.cgi?id=2030932
--- Comment #69 from Jonathan Christison <jochrist(a)redhat.com> ---
Marking Red Hat Build of Quarkus as not affected, the product neither ships nor
uses log4j 2.x and instead relies on Jboss Logging, furthermore log4j is
excluded from the quarkus BOM.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2030932
https://bugzilla.redhat.com/show_bug.cgi?id=2030932
--- Comment #67 from Stoyan Nikolov <snikolov(a)redhat.com> ---
Red Hat Virtualization ships rhvm-appliance which includes a vulnerable version
of log4j released by Red Hat EAP. Once EAP releases a fixed version of the
package Red Hat Virtualization users can consume the fix with a regular update
via the package manager inside the rhvm-appliance.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2030932