Project

General

Profile

Actions

Bug #5062

closed

Not keyword matches in Kerberos requests

Added by Jeff Lucovsky almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

I was doing some tests with the following rule:

alert krb5 any any -> any any (msg:"Kerberos 5"; krb5_msg_type:10;)

But I was unable to make it work against the pcap I sent you, which is only a Kerberos request (AS-REQ) and response (AS-REP).

After digging for a while in the code there was discovered that this may happen cause in the https://github.com/OISF/suricata/blob/master/rust/src/krb/krb5.rs#L123 file no transaction is created by Kerberos requests, so they are ignored by any Kerberos keyword (I've also tested with the krb5_sname).

alert krb5 any any -> any any (msg:"Kerberos 5"; krb5_sname; content:"krbtgt"; sid:5; rev:1;)

Thanks for this great software


Files

as-rep-as-req.pcapng (2.64 KB) as-rep-as-req.pcapng Eloy Pérez, 06/15/2021 02:45 PM
krb5-msg-type-test.pcapng (16 KB) krb5-msg-type-test.pcapng Eloy Pérez, 10/21/2021 10:20 AM

Related issues 1 (0 open1 closed)

Copied from Suricata - Bug #4529: Not keyword matches in Kerberos requestsClosedEloy PérezActions
Actions #1

Updated by Jeff Lucovsky almost 3 years ago

  • Copied from Bug #4529: Not keyword matches in Kerberos requests added
Actions #2

Updated by Philippe Antoine almost 3 years ago

  • Status changed from Assigned to Closed
Actions

Also available in: Atom PDF