added
Log4Shell prevention rules for AWS, Azure, and GCP added ⚠️
over 2 years ago by Gilad Mark
Using a vulnerable version of the Apache Log4j library might enable attackers to exploit a Lookup mechanism that enables remote code execution. We’ve added rules to check that your cloud WAFs have the right signatures in place to prevent Log4j exploits (also known as Log4Shell). We’ve added the following policies:
- AWS WAFv2 (CKV_AWS_192)
- Azure Web Application Gateway (CKV_AZURE_135)
- Azure Front Door WAF (CKV_AZURE_133)
- GCP Cloud Armor (CKV_GCP_73)