On 31/03/2022 12:25, Rémy Maucherat wrote:
On Thu, Mar 31, 2022 at 1:16 PM Mark Thomas wrote:
On 31/03/2022 11:48, Rémy Maucherat wrote:
On Thu, Mar 31, 2022 at 11:52 AM Mark Thomas wrote:
Hi all,
My recent hardening fix to the class loader [1] provides mitigation for
a current Spring
On 31/03/2022 12:33, Konstantin Kolinko wrote:
чт, 31 мар. 2022 г. в 12:52, Mark Thomas :
Hi all,
My recent hardening fix to the class loader [1] provides mitigation for
a current Spring vulnerability [2].
While this is a Spring vulnerability, it may be the case for some users
that updating T
чт, 31 мар. 2022 г. в 12:52, Mark Thomas :
>
> Hi all,
>
> My recent hardening fix to the class loader [1] provides mitigation for
> a current Spring vulnerability [2].
>
> While this is a Spring vulnerability, it may be the case for some users
> that updating Tomcat is an easier mitigation path th
On Thu, Mar 31, 2022 at 1:16 PM Mark Thomas wrote:
>
> On 31/03/2022 11:48, Rémy Maucherat wrote:
> > On Thu, Mar 31, 2022 at 11:52 AM Mark Thomas wrote:
> >>
> >> Hi all,
> >>
> >> My recent hardening fix to the class loader [1] provides mitigation for
> >> a current Spring vulnerability [2].
>
On 31/03/2022 11:48, Rémy Maucherat wrote:
On Thu, Mar 31, 2022 at 11:52 AM Mark Thomas wrote:
Hi all,
My recent hardening fix to the class loader [1] provides mitigation for
a current Spring vulnerability [2].
While this is a Spring vulnerability, it may be the case for some users
that upda
On Thu, Mar 31, 2022 at 11:52 AM Mark Thomas wrote:
>
> Hi all,
>
> My recent hardening fix to the class loader [1] provides mitigation for
> a current Spring vulnerability [2].
>
> While this is a Spring vulnerability, it may be the case for some users
> that updating Tomcat is an easier mitigati
