unsupported suricata 8 sticky buffers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
Research direction
Start by locating the sticky buffer parser and its tests; the issue does not name specific files or test cases. Check how the listed Suricata 8 buffer names are represented, including the noted underscored forms. Done means rules using the listed names parse successfully, with tests covering the previously unsupported buffers.
Written by the indexing model from the issue text.
Description
gonids is missing support for quite a few sticky buffers as of suricata 8. I've hit parse failures on the following:
mqtt.connect.password
mqtt.connect.username
mqtt.publish.message
mqtt.publish.topic
file.name
smtp.rcpt_to
websocket.payload
for completeness, here's the complete list of unsupported sticky buffers:
dnp3.data
dns.additionals.rrname
dns.answer.name
dns.answers.rrname
dns.authorities.rrname
dns.queries.rrname
dns.query.name
dns.response.rrname
email.cc
email.date
email.from
email.message_id
email.received
email.subject
email.to
email.url
email.x_mailer
enip.product_name
enip.service_name
file.name
ftp.completion_code
ftp.reply
ike.init_spi
ike.key_exchange_payload
ike.nonce_payload
ike.resp_spi
ike.vendor
krb5.cname
krb5.sname
ldap.request.attribute_type
ldap.request.dn
ldap.responses.attribute_type
ldap.responses.dn
ldap.responses.message
mdns.additionals.rrname
mdns.answers.rrname
mdns.authorities.rrname
mdns.queries.rrname
mdns.response.rrname
mqtt.connect.clientid
mqtt.connect.password
mqtt.connect.protocol_string
mqtt.connect.username
mqtt.connect.willmessage
mqtt.connect.willtopic
mqtt.publish.message
mqtt.publish.topic
mqtt.subscribe.topic
mqtt.unsubscribe.topic
ntp.reference_id
pgsql.query
rfb.name
sdp.attribute
sdp.bandwidth
sdp.connection_data
sdp.email
sdp.encryption_key
sdp.media.connection_data
sdp.media.encryption_key
sdp.media.media
sdp.media.media_info
sdp.origin
sdp.phone_number
sdp.repeat_time
sdp.session_info
sdp.session_name
sdp.time
sdp.timezone
sdp.uri
sip.content_length
sip.content_type
sip.from
sip.protocol
sip.request_line
sip.response_line
sip.stat_code
sip.stat_msg
sip.to
sip.user_agent
sip.via
smb.named_pipe
smb.ntlmssp_domain
smb.ntlmssp_user
smb.share
smtp.helo
smtp.mail_from
smtp.rcpt_to
snmp.usm
tls.alpn
tls.random_bytes
tls.random_time
tls.subjectaltname
websocket.payload
A couple of these (smb.named_pipe, smb.share, krb5.cname and krb5.sname) are supported in an underscored form.
Thanks for the help! For context, I'm trying to parse the Vulncheck initial access rule set to do some mechanical manipulations.
- Dominant language
- Go
- Stars
- 197
- Forks
- 52
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/gonids
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
google/gonids#251 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
Maintainers usually reply within 1 day
Similar issues
-
compress: block buffers get re-zeroed on every call, and the zeroing is immediately overwrittenOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/ch-go#1218 ·
Maintainers usually reply within 13 days
-
effort:s impact:low raised-by:reviewer risk:low
Difficulty 1/5 Under an hour Newbie friendliness 84/100
medici-finance/assay#4251 · 1 comment ·
Maintainers usually reply within 1 day
-
automation models
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
golang-migrate/migrate#1457 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day