Is community impacted by Log4J vulnerability?
Is Khoros community compaged by this log4j vulnerability: CVE-2021-44228
Forum Discussion
tyw wrote:I think the issue you're seeing is related to Web Application Firewall (WAF) changes that may have been made on your site. We hit this with the word 'localhost'. No matter what we did, that word caused a 403 error.
After checking in with Support they asked me to review the WAF email and sure enough that was the culprit.
The 403 forbidden error is definitely because of the WAF, and rightly so!
It's basically the 1st line of defense in preventing any kind of attack using the Log4Shell vulnerability. The WAF blocks "jndi" followed by ":" because that is a must in the string used to start the attack.
So even if you have a vulnerable server, the server will not receive any malicious strings because you're blocking it before it even gets sent to the server.
