Is Cromwell affected by log4shell ?
See original GitHub issueA simple grep through the source code reveals several hits with Log4j:
CromwellRefdiskManifestCreator/pom.xml: <groupId>org.apache.logging.log4j</groupId>
CromwellRefdiskManifestCreator/pom.xml: <artifactId>log4j-core</artifactId>
CromwellRefdiskManifestCreator/pom.xml: <groupId>org.apache.logging.log4j</groupId>
CromwellRefdiskManifestCreator/pom.xml: <artifactId>log4j-api</artifactId>
CromwellRefdiskManifestCreator/src/main/java/org/broadinstitute/manifestcreator/CromwellRefdiskManifestCreatorApp.java:import org.apache.logging.log4j.Level;
CromwellRefdiskManifestCreator/src/main/java/org/broadinstitute/manifestcreator/CromwellRefdiskManifestCreatorApp.java:import org.apache.logging.log4j.LogManager;
CromwellRefdiskManifestCreator/src/main/java/org/broadinstitute/manifestcreator/CromwellRefdiskManifestCreatorApp.java:import org.apache.logging.log4j.Logger;
CromwellRefdiskManifestCreator/src/main/java/org/broadinstitute/manifestcreator/CromwellRefdiskManifestCreatorApp.java:import org.apache.logging.log4j.core.config.Configurator;
project/Dependencies.scala: // Replace all log4j usage with slf4j
project/Dependencies.scala: // https://www.slf4j.org/legacy.html#log4j-over-slf4j
project/Dependencies.scala: "org.slf4j" % "log4j-over-slf4j" % slf4jV
I wasn’t able to expose a vulnerability by using malicious code but my test is probably not extensive. It looks like this lib is used in a packaging tool of Cromwell so probably not executed during production. On the other hand, slj4j seems to be used everywere. Is that abstraction layer vulnerable ?
Could you please let us know if you believe Cromwell is affected by Log4shell ?
Thanks,
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
What is Log4Shell, and How Can You Tell if You're Affected?
The Mirantis team has confirmed that most of our products are unaffected by the vulnerability; the few issues we found were of low...
Read more >RHSB-2021-009 Log4Shell - Remote Code Execution - log4j ...
Hi RHEL 7 is not impacted by CVE-2021-44228 - which is also known as Log4Shell - and a Critical severity RCE flaw within...
Read more >Mitigating Log4Shell and Other Log4j-Related Vulnerabilities
Log4Shell, disclosed on December 10, 2021, is a remote code execution (RCE) vulnerability affecting Apache's Log4j library, versions 2.0-beta9 ...
Read more >Log4Shell Zero-Day Vulnerability - CVE-2021-44228 - JFrog
In this technical blog post, we will clarify the exploitation vectors for this issue, provide accurate research-backed novel information on ...
Read more >Log4Shell Anniversary: One Year Later, What Has Changed?
Recap: What is the Log4Shell Vulnerability and Why Was it Significant? · Huge attack surface – Millions of vulnerable Java applications worldwide ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We redundantly re-verified the absence of the problem class [0] by unzipping the shipping Cromwell JAR and manually checking that the path is empty.
[0]
org/apache/logging/log4j/core/lookup/JndiLookup.class
Cromwell itself does not use Log4j.
This can be verified by executing
sbt dependencyTree
and noting that all instances of “log4j” occur inorg.slf4j:log4j-over-slf4j
which is a Log4j compatibility bridge from a different project.The utility tool
CromwellRefdiskManifestCreator
is written in Java and does use Log4j. It is not included in the Cromwell JAR. It is being updated presently.