Yes! To start, our customers using the JFrog DevOps Platform as a central part of their mission-critical software development lifecycle (SDLC) process already have everything needed to quickly remediate against the log4j vulnerability.
With your accumulated packages, binaries, images, and metadata under Artifactory’s binary repository management, you can search artifacts and builds to discover every usage of the log4j package, including as transitive dependencies, across your entire software supply chain. And you can create Xray policies and watches to block any further builds using vulnerable versions of the log4j package from production.
For the developer community at large, JFrog has also released a helpful set of open source tools to identify log4j use in both source code and binaries in local directories.