log4j-core vulnerabilities being detected is a false positive.
We found this log4j vulnerabilities in 'deepfenceio/deepfence_elastic_ce' if log4j issue is already resolved in 1.3.0 release, why deepfence console is still flagging it.
As per slack conversation log4j-core vulnerabilities being detected is a false positive. Since the elasticsearch didn't send the patch for the elasticsearch-oss-no-jdk. So team already removed the vulnerable class(JndiLookup.class) from the jar, so the final image does not have log4j related vulnerabilities but still deepfence console is flagging it. Team is working on getting false-positive fixed.
Raising this issue to keep track on progress.
@sidd0529 would verify if we still getting the false positives?
this issue has been fixed, @ak12021996 can you pls check it. Closing this issue reopen if needed