Project

General

Profile

Actions

Bug #3810

closed

Missing community ID in smb, rdp, tftp, dhcp

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

Status:
Closed
Priority:
High
Assignee:
Target version:
Affected Versions:
Effort:
Difficulty:
Label:

Description

The function JsonAddCommonOptions is not called in SMB, RDP, TFTP and DHCP protocols resulting in Community ID not to be present even if asked.

In the case of SMB and RDP this is clearly missing. For TFTP and DHCP, this could be discussed as we have no real flow. But other tools should be able to build the same community ID so it seems ok to have it.


Related issues 1 (0 open1 closed)

Copied from Suricata - Bug #3339: Missing community ID in smb, rdp, tftp, dhcpClosedJeff LucovskyActions
Actions #1

Updated by Jeff Lucovsky almost 4 years ago

  • Copied from Bug #3339: Missing community ID in smb, rdp, tftp, dhcp added
Actions #2

Updated by Jeff Lucovsky almost 4 years ago

  • Assignee changed from Shivani Bhardwaj to Jeff Lucovsky
Actions #3

Updated by Jeff Lucovsky almost 4 years ago

  • Status changed from Assigned to In Review
Actions #5

Updated by Jeff Lucovsky almost 4 years ago

  • Status changed from In Review to Closed
Actions

Also available in: Atom PDF