
#cybersecurity #respectdata Click to Tweet Rezilion found that most #Log4j scanners had blindspots and were limited by the testing method, thus failing to detect vulnerabilities in all file formats. Consequently, the agency’s Log4j scanner carried a disclaimer that the information and code in the repository was provided on the “as is” basis. Similarly, CISA acknowledged the limitation of its Log4j scanner, adding that there were other use cases that threat actors could exploit Log4j vulnerabilities. “And in the case of Log4j, there are a lot of edge instances in many places.” “Security leaders cannot blindly assume that various open-source or even commercial-grade tools will be able to detect every edge case,” Perkal wrote. Additionally, Rezilion noted that various Log4j scanners had blindspots and were limited by the detection, method making them less effective. Surprisingly, they discovered that out of nine frequently used Log4j scanners tested, none could detect vulnerability in all file formats. According to the company’s security researcher Yotam Perkal, most Log4j scanners failed because Java files could be packaged several layers deep into other files in different formats. Meanwhile, Rezilion tested several Log4j scanners and discovered that they had varying degrees of effectiveness.

In addition to CISA, the CERT Coordination Center, CrowdStrike, Tenable, Trend Micro, and other cybersecurity firms released similar Log4j scanners to detect vulnerabilities in Log4j deployments.


Most published Log4j scanners fail to detect vulnerabilities across file formats Additionally, vendors should inform their end-users of vulnerable products.
#Log4j network scanner Patch
In the joint cybersecurity advisory, the agencies direct public and private organizations to identify and patch the critical vulnerability in the Log4j library used in applications, review their security posture, and report compromises to the FBI or CISA. Unlike other Log4j scanners with 3-4 headers, CISA’s tool covers over 60 HTTP request headers, supports DNS callback for the Log4shell vulnerability discovery and validation, lists of URLs, WAF Bypass payloads, and fuzzing for HTTP POST data and JSON data parameters.
