You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the named decoder assumes entries to look like (as mentioned in decoder.xml): valhalla named[7885]: client 192.168.1.231#1142: update 'hayaletgemi.edu/IN' denied
BUT on Ubuntu 20.04 the log entries have an additional ID starting with "@":
Oct 26 00:00:53 valhalla named[43400]: client @0x7f2b78046e40 76.188.251.143#80 (sl): query (cache) 'sl/ANY/IN' denied
Oct 26 00:00:53 valhalla named[43400]: client @0x7f2b78046e40 76.188.251.143#80 (sl): query failed (REFUSED) for sl/IN/ANY at query.c:5425
When testing such a string the output in Phase 2 has no srcip in it and cannot block the attack:
This decoder correctly decodes the src ip again.
It ignores older logs though, we could probably devise a way to cover
both, but I'm not convinced it is worth it.
from ogmueller in issue ossec#1927
Version:
Ubuntu 20.04.1 LTS
Package: ossec-hids-server
Version: 3.6.0-14954focal
Currently the named decoder assumes entries to look like (as mentioned in decoder.xml):
valhalla named[7885]: client 192.168.1.231#1142: update 'hayaletgemi.edu/IN' denied
BUT on Ubuntu 20.04 the log entries have an additional ID starting with "@":
When testing such a string the output in Phase 2 has no
srcip
in it and cannot block the attack:If decoder.xml is changed to:
Phase 2 output is correct including
srcip
:The text was updated successfully, but these errors were encountered: