-
Notifications
You must be signed in to change notification settings - Fork 173
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problem with option #204
Comments
Since you appear to be running on Windows, I'll mention that using 'syslog' on Windows systems is uncommon and not default - this is not for writing to the System Event Log, but for sending events to a 'syslog' server, much more common in Linux and UNIX deployments. In that case, the option your last example is almost correct, except one would not use the square brackets in the actual command line, but only for illustrating the example syntax. If you actually had a Syslog server on the 192.168.9.80 address, listening on UDP port 5544, you would use |
ok. Microsoft Windows [version 6.3.9600] C:\Users\administrateur>cd c:\temp c:\temp>log4j2-scan --all-drives --syslog-udp 192.168.9.80:5544 c:\temp> |
@jvirot You should use latest version (v2.6.2). |
ok, last questions, i have 0 vulnerability after scan. i supose no log was sent to my syslog because i reveive nothing, do i hae an option to send syslog with or without vulnerability? i don't understand this option, it's a numberf? |
@jvirot Would you open a new enhancement issue? |
just want to know if it's normal or not to not have syslog report iwth 0 vulnérability and how to send with 0 vulnerability |
@jvirot Scanner doesn't send any report if no vulnerable log4j found. (it's normal). You cannot send syslog for 0 vulnerability. thus needs new issue. |
i try a scan with log4j1 option ans i have vulnerability... but i don't receive syslog ( i have a nagios syslog) and no problem with firewall i check with portqry and the result is listening c:\temp>log4j2-scan.exe --all-drives --syslog-udp 192.168.9.80:5544 --syslog-level alert --scan-log4j1 --scan-logback Running scan (10s): scanned 349 directories, 6253 files, last visit: C:\Program Scanned 67209 directories and 320812 files c:\temp> |
Check outgoing syslog packets using wireshark first. icmp response can be filtered when you are checking udp port using portqry. |
I just check my packets with wireshark and on my firewall and nothing was sending |
@jvirot My test output on v2.6.3 (expected output)
If scanner cannot send syslog, it should print error message like this:
|
it's ok, i receive syslog now... after a reboot of the 2012R2 machine.... windows bug ! ;-) Found 8 potentially vulnerable files, but in my syslog i have only one entrie.... the last one Microsoft Windows [version 6.3.9600] C:\Users\administrateur>cd c:\temp\log4j2 c:\temp\log4j2>log4j2-scan --all-drives --syslog-udp 192.168.9.80:5544 --syslog- Running scan (10s): scanned 345 directories, 6367 files, last visit: C:\Program Scanned 67261 directories and 321409 files c:\temp\log4j2> |
@jvirot Finally.. You did it! Maybe last screenshot means unexpected syslog drops.. Some open source daemons cannot receive all syslog packets due to garbage collection stall. If you have more time, wait HTTPS POST logging feature (maybe.. next week) |
hello
i try a lot of this to perfom syslog option but i don't understand how to write this
Microsoft Windows [version 6.3.9600]
(c) 2013 Microsoft Corporation. Tous droits réservés.
c:\temp>log4j2-scan --all-drives
Logpresso CVE-2021-44228 Vulnerability Scanner 1.3.2 (2021-12-15)
Scan drives: C:,D:
^C
c:\temp>log4j2-scan --all-drives --syslog-udp
Logpresso CVE-2021-44228 Vulnerability Scanner 1.3.2 (2021-12-15)
Scan drives: C:,D:
^C
c:\temp>log4j2-scan --all-drives --syslog-udp 192.168.9.80:5544.
Error: unsupported option: --syslog-udp
c:\temp>
c:\temp>log4j2-scan --all-drives --syslog-udp [192.168.9.80:5544]
Error: unsupported option: --syslog-udp
c:\temp>
c:\temp>log4j2-scan --all-drives --syslog-udp[192.168.9.80:5544]
Logpresso CVE-2021-44228 Vulnerability Scanner 1.3.2 (2021-12-15)
Scan drives: C:,D:\
Scanned 67767 directories and 320512 files
Found 0 vulnerable files
Completed in 80.81 seconds
c:\temp>
The text was updated successfully, but these errors were encountered: