Comment by wandering-nomad

OP here. What is the quickest way to fix it? Given the ubiquity of Log4j, this seems to be a problem that lot of folks must be racing to fix