JAVA_DLDR.XPL

October 09, 2012
 Analysis by: Michael Cabel
 PLATFORM:

Windows 2000, Windows XP, Windowa Server 2003

 OVERALL RISK RATING:
 DAMAGE POTENTIAL:
 DISTRIBUTION POTENTIAL:
 REPORTED INFECTION:

  • Threat Type: Trojan

  • Destructiveness: No

  • Encrypted: No

  • In the wild: Yes

  OVERVIEW

Once a malware successfully exploits the said vulnerability, it causes certain actions to be done on the system.

This Trojan may arrive bundled with malware packages as a malware component.

  TECHNICAL DETAILS

File Size:

Varies

File Type:

Java Class

Initial Samples Received Date:

14 Jul 2011

Arrival Details

This Trojan may arrive bundled with malware packages as a malware component.

Download Routine

This Trojan takes advantage of the following software vulnerabilities to download possibly malicious files:

  • Java Runtime Environment

Other Details

More information on this vulnerability can be found below:

  • http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0840

NOTES:

Once a malware successfully exploits the said vulnerability, it causes the following actions to be done on the system:

  • A remote host may execute an arbitrary code that attempts to download and execute a malicious file from a specified URL.

  SOLUTION

Minimum Scan Engine:

8.900

FIRST VSAPI PATTERN FILE:

8.288.12

FIRST VSAPI PATTERN DATE:

14 Jul 2011

Step 1

For Windows XP and Windows Server 2003 users, before doing any scans, please make sure you disable System Restore to allow full scanning of your computer.

Step 2

Scan your computer with your Trend Micro product to delete files detected as JAVA_DLDR.XPL. If the detected files have already been cleaned, deleted, or quarantined by your Trend Micro product, no further step is required. You may opt to simply delete the quarantined files. Please check this Knowledge Base page for more information.

Step 3

Download and apply this security patch Refrain from using these products until the appropriate patches have been installed. Trend Micro advises users to download critical patches upon release by vendors. http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0840


Did this description help? Tell us how we did.