Project

General

Profile

Actions
Copy link

Bug #3804

closed

Missing community ID in smb, rdp, tftp, dhcp

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

Status:
Closed
Priority:
High
Assignee:
Jeff Lucovsky
Target version:
5.0.4
Affected Versions:
5.0.0
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 open — 1 closed)

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

Updated by Jeff Lucovsky almost 4 years ago

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

Updated by Jeff Lucovsky almost 4 years ago

  • Status changed from Assigned to In Review
Actions
Copy link
 #3

Updated by Jeff Lucovsky over 3 years ago

  • Status changed from In Review to Closed
Actions
Copy link

Also available in: Atom PDF