[BUG] Verifying that cve-2021-44228 (Apache Log4J / Log4Shell) does not affect openapi-generator
See original GitHub issueDescription
This is a general request for a statement. I am not a java dev but looking through the code dependencies, this project relies on slf4j for logging and not Log4J 2
. Am I reading everything correctly?
openapi-generator version
Current Master version 5.3.0
Issue Analytics
- State:
- Created 2 years ago
- Reactions:5
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Guidance for preventing, detecting, and hunting for ... - Microsoft
The remote code execution (RCE) vulnerabilities in Apache Log4j 2 referred to as “Log4Shell” (CVE-2021-44228, CVE-2021-45046, CVE-2021-44832) ...
Read more >Exploiting, Mitigating, and Detecting CVE-2021-44228: Log4j ...
The CVE-2021-44228 is a CRITICAL vulnerability that allows attackers to execute arbitrary code on a machine. Updating log4j to 2.16.0.
Read more >Apache JSPWiki Log4Shell Direct Check (CVE-2021-44228)
The version of Apache JSPWiki running on the remote web server is affected by a remote code execution vulnerability in the bundled Apache...
Read more >Simulating and Preventing CVE-2021-44228 Apache Log4j ...
In this blog, the CVE-2021-44228 Apache Log4j vulnerability, Log4j exploit payload examples, simulation and remediation of Log4j attacks are ...
Read more >Known Issue for CVE-2021-44228 - PaperCut
Hitting a problem with your PaperCut implementation? You might not be alone! ... Log4j RCE vulnerability 'Log4Shell' (CVE-2021-44228). 21.0 and later.
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
Piggy-backing on this as it’s related. Creating a custom generator produces a
pom.xml
containing this segment indicating that it’s using Maven Surefire w/log4j.command:
openapi-generator-cli meta -n custom-generator -p com.company.custom
I don’t know enough about Java to figure out which version of log4j is used. It looks like it’s only for running tests, so I don’t believe it gets included in the jar file the gets produced when packaged.
Same goal as OP. A statement would be appreciated.
Scanning with log4j-detect yields a positive result: