search

mergebase / log4j-detector

A public open sourced tool. Log4J scanner that detects vulnerable Log4J versions (CVE-2021-44228, CVE-2021-45046, etc) on your file-system within any application. It is able to even find Log4J instances that are hidden several layers deep. Works on Linux, Windows, and Mac, and everywhere else Java runs, too! TAG_OS_TOOL, OWNER_KELLY, DC_PUBLIC
Other
638 stars 98 forks source link

Strange Exceptions #13

Closed chgad closed 2 years ago

chgad commented 2 years ago

I'm confronted with a (until now) partial analysis which states a few RuntimeExceptions as follows:

-- Analyzing paths (could take a long time).
-- Note: specify the '--verbose' flag to have every file examined printed to STDERR.
-- Problem: /dev/agpgart - java.lang.RuntimeException: java.io.IOException: Invalid argument
-- Problem: /dev/autofs - java.lang.RuntimeException: java.io.IOException: Invalid argument
-- Problem: /dev/bsg/0:0:0:0 - java.lang.RuntimeException: java.io.IOException: Invalid argument
-- Problem: /dev/bsg/3:0:0:0 - java.lang.RuntimeException: java.io.IOException: Invalid argument
-- Problem: /dev/btrfs-control - java.lang.RuntimeException: java.io.IOException: Invalid argument

Do they have anything to do with actual hits or are they caused due to being devices?

(Maybe related to #8)

juliusmusseau commented 2 years ago

I've applied the suggested fix for #8. Devices will be skipped now (and "--verbose" will mention that they are being skipped).