#Screaming frog seo spider log4j update#

Update (Dec 16th 2021 - 16:00 UTC): Incomplete fix for CVE-2021-44228 results in a DoS condition under special configurations. v2.16.0 did not fix a recursive self referential lookup under special configurations. Update (Dec 18th 2021 - 14:00 UTC): Apache Log4j2 v2.17.0 released to fix a Denial of Service vulnerability. The product does not use any log4j components so its not vulnerable. Update (Dec 20th 2021 - 12:00 UTC): Link-Assistant support replies to a question about whether their product is vulnerable to the Log4j CVE-2021-44228 vulnerability. Update (Dec 20th 2021 - 12:00 UTC): Screamingfrog releases version 16.0 of the SEO Spider product on 14th December 2021 to mitigate the Log4j CVE-2021-44228 vulnerability Please share this with your customers, internal teams and other stakeholders. Update (Dec 20th 2021 - 12:30 UTC): We are releasing an updated one pager. Tool is available for Ubuntu, Debian and Amazon Linux. A tool that injects an agent into a running JVM to patch JNDI lookups. Update (Dec 24th 2021 - 03:00 UTC): The Amazon Corretto team released a hotpatch for Apache log4j on 12th Dec 2021. If, as part of mitigation, you have removed the JNDI class altogether from log4j JARs, you are already protected. The bug requires attacker to control configuration for any effect. Apache has released v2.17.1 to mitigate this. Update (Dec 29th 2021 - 02:20 UTC): A new vulnerability with a moderate severity was identified and assigned CVE-2021-44832.

Screaming frog seo spider log4j