Open
Description
Optionally update the Email Template and Theme API to take a base64 encoded version of the FTL template
Description
In FusionAuth Cloud we've seen the AWS WAF cause a false positive when using a LOG4J RCE detection rule for the API request body.
AWS has indicated it is working as designed (lame).
One option to consider would be to update any API that takes an FTL template such as the Email Template API and the Theme API to optionally take a base64 encoded version of the template to avoid pattern matching rules such as what AWS is using in their WAF rules.
Seems a bit heavy handed, but this would allow us to further obfuscate the markup language that can reasonably contain parameterized strings which it appears can potentially match an RCE filter.
Community guidelines
All issues filed in this repository must abide by the FusionAuth community guidelines.