DDI RULE 1656


 DESCRIPTION NAME:

CVE-2014-6271 - Shellshock DHCP Exploit

 CONFIDENCE LEVEL:
 SEVERITY INBOUND:
 SEVERITY OUTBOUND:
Informational
Low
Medium
High

  OVERVIEW

This is Trend Micro detection for SMTP network protocol that manifests exploit activities and can be used for Point of Entry or Lateral Movement.

The host exhibiting this type of network behavior is likely compromised by malware, or being used by a malicious insider to gain unauthorized access to other hosts in the network.

  TECHNICAL DETAILS

Attack Phase: Point of Entry or Lateral Movement

Protocol: SMTP

Risk Type: OTHERS
(Note: OTHERS can be network connections related to hacking attempts, exploits, connections done by grayware, or suspicious traffic.)

Threat Type: Exploit

Confidence Level: High

Severity: Medium(Inbound)| High(Outbound)

DDI Default Rule Status: Enable

Event Class: Exploit

Event Sub Class: Command Injection

Behavior Indicator: Exploit

APT Related: NO

CVE Exploit: CVE-2014-6271

The following malware families are related to this detection:

  • PERL_SHELBOT.SMO
  • PERL_SHELLBOT.CD
  • PERL_SHELLBOT.DI
  • ELF_BASHLITE.E
  • ELF_BASHLITE.J
  • ELF_BASHLITE.A
  • SHELLSHOCK
  • ELF_BASHLITE.SM

  SOLUTION

Network Content Inspection Pattern Version: 1.12227.00
Network Content Inspection Pattern Release Date: 04 Dec 2014
Network Content Correlation Pattern Version: 1.12199.00
Network Content Correlation Pattern Release Date: 04 Dec 2014

Immediate Action

  • Change all passwords of the host and ensure the use of strong passwords.
  • Strong passwords should contain upper case letters, lower case letters, digits, punctuation marks, and other symbols. Remove any unrecognizable files, software, or services.
  • Update your Trend Micro products and pattern files to the latest version.
  • Scan the host for possible malware detection and to clean any detected items.

Secondary Action

To prevent future exploits, ensure that the host and others visible to the external network have their browsers, plugins, and operating systems fully updated with the latest patches. Also, use virtual patching even if the needed patch is still not available for deployment.


Did this description help? Tell us how we did.