It turns out while putting together a TL;DR analysis of ESAPI and Log4Shell (which I expect to be sending out soon), that I realized that I forgot to mention a CVE regarding Log4J 1.x that I just noticed.
If you are still using the deprecated Log4J 1.x logging with ESAPI, please read this new security bulletin:
(which applies to all versions of ESAPI) to make sure that you are not vulnerable.
--