You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,7 +27,7 @@ Scanner that detects vulnerable Log4J versions to help teams assess their exposu
27
27
# Introduction <aname="itemdetector"></a>
28
28
29
29
Currently reports [log4j-core](https://repo1.maven.org/maven2/org/apache/logging/log4j/log4j-core/) versions 2.3.1, 2.12.3, and 2.17.0 as **\_SAFE\_**, 2.12.2, 2.15.0 and 2.16.0 as **\_OKAY\_** and all other versions as **\_VULNERABLE\_**
30
-
(although it does report pre-2.0-beta9 as **\_POTENTIALLY_SAFE\_**). It reports older log4j-1.x[log4j/log4j](https://repo1.maven.org/maven2/log4j/log4j/) versions as **\_OLD\_**.
30
+
(although it does report pre-2.0-beta9 as **\_POTENTIALLY_SAFE\_**). It reports older [log4j-1.x](https://repo1.maven.org/maven2/log4j/log4j/) versions as **\_OLD\_**.
31
31
32
32
Can correctly detect log4j inside executable spring-boot jars/wars, dependencies blended
33
33
into [uber jars](https://mergebase.com/blog/software-composition-analysis-sca-vs-java-uber-jars/), shaded jars, and even
0 commit comments