#Whatsapp 2.12.1 jar upgrade#
#Whatsapp 2.12.1 jar full#
#Whatsapp 2.12.1 jar android#

Added data parsing from FaceApp (3.4.9) from Apple iOS devices and FaceApp (3.4.12.1) from Android devices. Added data parsing from WhatsApp Business (2.19.80) from Apple iOS devices. The total amount of supported versions exceeds 11,400+! Added data parsing from 200+ new app versions from Apple iOS and Android devices.

(C) Copyright 2021 Mergebase Software Inc. Must be valid JSON.Įxample: –exclude='’Įxit codes: 0 = No vulnerable Log4J versions found.ġ = At least one legacy Log4J 1.x version found.Ģ = At least one vulnerable Log4J version found.Ībout – MergeBase log4j detector (version 2021.12.29)

#Whatsapp 2.12.1 jar full#

–exclude=X – Where X is a JSON list containing full paths to exclude.

–stdin – Read STDIN for paths to explore (one path per line) Make sure it was someone in your team or company that removed “JndiLookup.class” if that’s the case, because attackers have been known to remove this file themselves to prevent additional competing attackers from gaining access to compromised systems. _POTENTIALLY_SAFE_ -> The “JndiLookup.class” file is not present, either because your version of Log4J is very old (pre 2.0-beta9), or because someone already removed this file.

#Whatsapp 2.12.1 jar upgrade#

_OLD_ -> You are safe from CVE-2021-44228, but should plan to upgrade because Log4J 1.2.x has been EOL for 7 years and has several known-vulnerabilities. _SAFE_ -> We currently only report this for Log4J versions 2.3.2, 2.12.4, and 2.17.1 (and greater). mergebase/log4j-detector v2021.12.29 (by ) analyzing paths (could take a while). We currently maintain a collection of log4j-samples we use for testing. Can correctly detect log4j inside executable spring-boot jars/wars, dependencies blended into uber jars, shaded jars, and even exploded jar files just sitting uncompressed on the file-system (aka *.class).