Project

General

Profile

Actions

Bug #5056

closed
JL

Bug #5037: invalid timestamp in ending events

invalid timestamp in ending events

Bug #5056: invalid timestamp in ending events

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

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
Effort:
Difficulty:
Label:

Description

When an event logging is triggered by the flow cleaning function, the timestamp is invalid as it is often set to a time that is before the flow start.


Files

smb-2-sessions.pcap (28.7 KB) smb-2-sessions.pcap Eric Leblond, 02/03/2022 10:54 AM

Related issues 1 (0 open1 closed)

Is duplicate of Suricata - Bug #5603: invalid timestamp in ending events (6.0.x backport)RejectedActions

JL Updated by Jeff Lucovsky about 4 years ago Actions #1

  • Copied from Bug #5037: invalid timestamp in ending events added

VJ Updated by Victor Julien almost 4 years ago Actions #2

  • Target version changed from 6.0.5 to 6.0.6

VJ Updated by Victor Julien almost 4 years ago Actions #3

  • Target version changed from 6.0.6 to 6.0.7

VJ Updated by Victor Julien over 3 years ago Actions #4

  • Target version changed from 6.0.7 to 6.0.8

VJ Updated by Victor Julien over 3 years ago Actions #5

  • Target version changed from 6.0.8 to 6.0.9

SB Updated by Shivani Bhardwaj over 3 years ago Actions #6

  • Status changed from Assigned to Rejected

SB Updated by Shivani Bhardwaj over 3 years ago Actions #7

  • Status changed from Rejected to New
  • Parent task set to #5037

VJ Updated by Victor Julien over 3 years ago Actions #8

  • Status changed from New to Rejected
  • Assignee deleted (Shivani Bhardwaj)
  • Target version deleted (6.0.9)

Duplicate of #5603

VJ Updated by Victor Julien over 3 years ago Actions #9

  • Is duplicate of Bug #5603: invalid timestamp in ending events (6.0.x backport) added
Actions

Also available in: PDF Atom