Aashish Sharma

Coredump-4.1.1 - zeek::detail::SerializationFormat::ReadData

3

After a long time I saw a crash on this cluster - posting here since this coredump does seem new Let me know if you want to look at the...

Variadic BIFs lack static type-check for fixed params

5

I made a very naive mistake and ended up with this crash/segfault. Instead of using Cluster::proxy_topic I mistakenly did Cluster::proxy_pool causing this crash. Here is a script to replicate it...

Coredump: 4.1.0 - Due to memory exhustion on the logger node

32

Logger node grows to 190GB and then crashes. There is no unusual change in traffic and I think this is a issue with 4.x.x and manifesting more on 4.1.x -...

4.1.0 - zeekctl worker restart does not preserve the files from the crashed worker-directory (stderr.log, stdout.log, prof.log etc)

1

Not sure if this issue is new or emerged somewhere in past - I just noticed it. This is a real problem if we setup a `zeekctl cron ` which...

I am afraid, I haven't zero'ed into the specific script to be able to say what is causing this coredump. I was in middle of adding/testing an IoC and this...

1) Updated the PayloadParts to have host as addr and port_ as port in…

6

…stead of string. This will be useful for callback detections! 2) Updated the parse_payload function to account for DNS name in the callback URL. eg: jndi:ldap://baddomain.xyz:1289/exploit This will be useful...

Segfault in 5.2.0: bad initializer, first operand should be a list

6

While trying some other code I stumbled across this construct which can trigger a segfault and a coredump. Here is backtrace: ``` Core was generated by `zeek ./a.zeek'. Program terminated...

Segfault - 5.2.1 Obj.h:179 zeek::Ref (o=0x0)

2

I noticed that my 5.2.1 run on FreeBSD 12.3-RELEASE-p11 crashed and here is the coredump. [ We did have a NFS outage - not sure if thats what caused this...

Crash 6.2.0 : Flare.cc: zeek::detail::bad_pipe_op

6

I have been seeing intermittent crashes in 6.2.0 with the following coredump: For reference: ``` (gdb) bt #0 0x0000000803888bca in thr_kill () from /lib/libc.so.7 #1 0x0000000803886f94 in raise () from...

zeekctl: Error: must run zeekctl on same machine as the manager node 127.0.0.1 vs 127.0.1.1

1

So, I saw this error when running zeekctl ( and zeekctl cron): ``` Error: must run zeekctl on same machine as the manager node. The manager node has IP address...