CVE-2021-44228-Scanner: Wrong format of the syslog messages
Your syslog message looks at the moment like this
<133>{"time": "2022-01-01 19:35:25+0100", "hostname": "checkmk", "path": "/usr/bin/pycharm/pycharm-community-2021.1.3/lib/log4j.jar", "entry": "", "product": "Log4j 1", "version": "1.2.17.2", "cve": "CVE-2021-4104", "status": "MITIGATED", "fixed": false}
Acording to RFC5424 the header (the stuff before the STRUCTURED-DATA/MESSAGE) should look like this
PRI VERSION SP TIMESTAMP SP HOSTNAME SP APP-NAME SP PROCID SP MSGID
followed by SP STRUCTURED-DATA [SP MSG]
(structured data must always be encoded in UTF-8). If the MESSAGE
is UTF-8 encoded it must start with the BOM (BOM = %xEF.BB.BF).
You are using only the PRI (Facility/Severity) field (<133>
) and the Message. This causes problems with some syslog implementations as the expect the message to be like in the RFC.
If you want to skip optional fileds you can use the NILVALUE (-
).
So your syslog message should look at least like this
<133> 1 - - - - - - {your message}
It would be nice to have the TIMESTAMP, HOSTNAME and APP-NAME populated like this (skipped PROCID, MSGID and STRUCTURED-DATA)
<133> 1 2022-01-01T23:20:50.52Z CHECKMK LOG4J-SCANNER - - - {your message}
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 18 (9 by maintainers)
Commits related to this issue
- Added --rfc5424 option. See #230 — committed to logpresso/CVE-2021-44228-Scanner by xeraph 2 years ago
- Added missing syslog invocation for scan error, Added file header to CSV log file. See #230 and #178 v2.7.1. — committed to logpresso/CVE-2021-44228-Scanner by xeraph 2 years ago
@xeraph I think this can be cosed 😃 (your typo is also gone)
works again. Perfect!
CHECKMKs syslog implementation looks fine now 😉 THX
so I need only discuss the non rfc5424 message handling with tribe29
@xeraph Great work 😃 I certainly will test it.
I was in the process of closing this, as after more digging the issue with the syslog implementaion of CHECKMK is not only because of the non rfc5424 formating. Guess I have to check this with the tribe29 guys anyway 😦
and now I will test all the new options 😃