Project

General

Profile

Actions

Bug #3103

closed

--engine-analysis warning for flow on an icmp request rule

Added by Peter Manev over 2 years ago. Updated almost 2 years ago.

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

Description

using latest git master at the moment of this report -

5.0.0-dev (3a91244 2019-07-22)

I have the following warning on

== Sid: 2027763 ==
alert icmp any any -> any any (msg:"ET TROJAN Possible ICMP Backdoor Tunnel Command - whoami"; itype:8; icode:0; content:"whoami"; depth:6; nocase; metadata: former_category TROJAN; reference:url,www.hackingarticles.in/command-and-control-tunnelling-via-icmp; classtype:trojan-activity; sid:2027763; rev:1; metadata:affected_product Windows_XP_Vista_7_8_10_Server_32_64_Bit, attack_target Client_Endpoint, deployment Perimeter, signature_severity Major, created_at 2019_07_29, performance_impact Moderate, updated_at 2019_07_29;)
    Rule matches on packets.
    Rule contains 1 content options, 0 http content options, 0 pcre options, and 0 pcre options with http modifiers.
    Fast Pattern "whoami" on "payload" buffer.
    Warning: Rule is inspecting both the request and the response.


where the rules is inspecting itype:8; icode:0;

Actions #1

Updated by Andreas Herz over 2 years ago

  • Assignee set to OISF Dev
  • Target version set to TBD
Actions #2

Updated by Victor Julien about 2 years ago

  • Status changed from New to Assigned
  • Assignee changed from OISF Dev to Jeff Lucovsky
  • Target version changed from TBD to 5.0.1
Actions #3

Updated by Jeff Lucovsky about 2 years ago

Since this is an ICMP echo (with code 0), the warning re: both request and response is invalid?

Currently, the analyzer is ICMP-agnostic and many, but not all, ICMP type values are request or response, but not both.

Please confirm that this is the concern.

Actions #4

Updated by Peter Manev about 2 years ago

Yes, thank you

Actions

Also available in: Atom PDF