Everything I’ve being reading about the log4j shell vulnerability all have the assumption that process is a flavor of a ‘webserver’ (i.e. a long running process that listens on ports).
I have a simple JAVA process that executes a series of operations (e.g. file manipulations), logs the processing with log4j and then terminates. Is there any exposure to injection in this scenario?
Not trying to avoid mitigation or remediation tasks but trying to prioritize my workload
I have a simple JAVA process that executes a series of operations (e.g. file manipulations), logs the processing with log4j and then terminates. Is there any exposure to injection in this scenario?
Not trying to avoid mitigation or remediation tasks but trying to prioritize my workload