For Home

Virus Profile: Exploit-CVE2012-0507

Threat Search
Print
   
Virus Profile information details
Risk Assessment: Home Low | Corporate Low
Date Discovered: 3/3/2012
Date Added: 3/3/2012
Origin: N/A
Length: varies
Type: Trojan
Subtype: Exploit
DAT Required: 6698
Removal Instructions
   
 
 
   

Description

An initial threat vector may be hosted on a website in the form of an Applet. The Applet would contain code to exploit CVE-2012-0507.The intent of the exploit is to surreptitiously download and execute additional malware on the infected system. An indication of this may be the presence unusual traffic to unknown domains. It was also observed to include an encrypted malware which is then dropped and installed on suuccessfull exploitation.

Unspecified vulnerability in the Java Runtime Environment component in Oracle Java SE JDK and JRE 5(update 33),6(Update 30) and 7(update 2) and earlier updates allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability via unknown vectors related to Scripting.

The vulnerability is in the implementation of the AtomicReferenceArray class that allows type safety checks to be circumvented to bypass the Java sandbox will permit Java to download and execute malware. The Applet typically contains code that consumes a URL Name (also a part of the Applet) which hosts the malware.

Aliases -

    • Microsoft - Exploit:Java/CVE-2012-0507.AX
    • NOD32 - Java/Exploit.CVE-2012-0507.AH

Indication of Infection

    • The exploit may download arbitrary files.
    • This exploit attempts to download and execute additional malware to the infected system.
    • The exploit may drop and install additional malware

Methods of Infection

    • This threat exploits an unpatched vulnerability in Sun Microsystems Java.
    • This Trojan can be installed while browsing compromised websites.
   

Virus Characteristics

----------------Updated on 18 March 2013----------------------

Aliases –
  • Fortinet       -    Java/Agent.NLG!exploit
  • Microsoft     -    Exploit:Java/CVE-2012-0507
  • Symantec   -    Trojan.Maljava
  • Nod32        -    Java/Exploit.Agent.NLG trojan
  • Avast          -    Java:CVE-2012-0507-WJ [Expl]


Characteristics – 

“Exploit-CVE2012-0507” is for Java applets that are written with malicious intention to Downloads other payloads and execute them without user consent. The applet malware exploits a Java Runtime Vulnerability as explained in exploit CVE-2012-0507.

The vulnerability present in the AtomicReference Array to bypass the java sandbox mechanism. The attacker crafts the class file with the serialized object data where it will trigger the vulnerability by deserializing the object array. The Vulnerability triggering class file is called by another class file which acts as a loader. Once it is exploited the loader class file will call another class file which will download the payload and execute it. 

This vulnerability is triggered due to the way error objects are handled by the vulnerable JavaScript engine. Normally Java Script Engines ensure that it executes only trusted code within the Java Runtime Environment as opposed to untrusted Applet code.

The exploit first creates an error object which the vulnerable Java Script Engine cannot handle, and then it executes a script that disables the

Java Security Manager using the "toString" method. It then throws an Exception and proceeds further and calls with the malicious class file to execute the arbitrary code.

In the wild, it can be found as a Java archive. The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.

The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.

The JAR file contains class files which triggers the Vulnerability and executes the arbitrary code to download other payloads
  • hw.class
  • BadRun.class
  • Hello.class
  • Indestuctable.class
  • LocalizeMem.class
  • NotebookNew.class
  • popers.class
  • Getter.class
Upon execution, the Trojan attempts to affects the vulnerability in Java Runtime Environment (JRE) and tries to connect the below URL to download other payload like PWS variants and root kit.
  • http://65.[Removed].185/099d99ad3cdf113b/099d99ad3cdf113b/q.php?gf=2w:1k:1g:1o:33&he=1i:31:32:1g:1n:1h:1l:1l:1n:31&h=1f&oo=u&kh=n&jopa=1943051
  • http://129.[Removed].15/6.exe
  • http://129.[Removed].15/1.exe?c=1
  • hxxp://65.[Removed].185/099d99ad3cdf113b/099d99ad3cdf113b/q.php?gf=2w:1k:1g:1o:33&he=1i:31:32:1g:1n:1h:1l:1l:1n:31&h=1f&oo=u&kh=n&jopa=1943051
  • hxxp://173.[Removed].16/gate.php
  • hxxp://129.[Removed].15/gate.php
  • hxxp://129.[Removed].15/6.exe
  • hxxp://129.[Removed].15/1.exe?c=1
  • hxxp://50.[Removed].70/app/geoip.js
  • hxxp://175.[Removed].181/api/urls/?ts=a2e2110f3ca79e32c9a8145341e7c7b78553b446&affid=46700
  • 15.[Removed].129
  • j.ma[Removed]nd.com
  • web-cd[Removed]de.com
  • firefi[Removed]ctory.com
  • 70.[Removed].50
  • 181.[Removed].175
  • 16.[Removed].173
  • 185.[Removed].65
  • 103.[Removed].68
  • 50.[Removed].70
  • 129.[Removed].15
  • 65.[Removed].185
  • static.r[Removed]e.softlayer.com
  • 92.[Removed].50
  • S010600[Removed]3d7.cg.shawcable.net

The following are the payloads dropped by the Trojan
  • %APPDATA%\Sun\Java\Deployment\cache\6.0\20\6a399854-11d8e749
  • %APPDATA%\Sun\Java\Deployment\cache\6.0\20\6a399854-11d8e749.idx
  • %Temp%\hsperfdata_Administrator\2552
  • %Temp%\105712187.exe
  • %Temp%\Content.IE5\GVE9QJU5\CAU7W5EZ.HTM
  • %Temp%\105712187.EXE
  • %Temp%\105715968.EXE
  • %Temp%\1943051.EXE
  • %Temp%\105722125.bat
  • %SYSTEMDRIVE%\RECYCLER\S-1-5-18\$8799278523af799c26e02500d72b61fb\n
  • %SYSTEMDRIVE%\RECYCLER\S-1-5-21-[Removed]\$698a2431bf10457d451afdf8d202d9b0\n

The following are the folders created in the system
  • %SYSTEMDRIVE%\RECYCLER\S-1-5-21[Removed]\$698a2431bf10457d451afdf8d202d9b0
  • %SYSTEMDRIVE%\RECYCLER\S-1-5-18

The following are the Registry key have been added to the system
  • HKEY_USERS\S-1-5-[Varies]\Software\Classes\CLSID\{GUID}
  • HKEY_USERS\S-1-5-[Varies]\Software\Classes\CLSID\{GUID}\InprocServer32
  • HKEY_USERS\S-1-5-[Varies]_Classes\CLSID\{GUID}
  • HKEY_USERS\S-1-5-[Varies]_Classes\CLSID\{GUID}\InprocServer32

The following are the Registry key values have been added to the system
  • HKEY_USERS\S-1-5-21-[Varies]\Software\WinRAR\HWID: 7B 33 31 44 38 33 39 43 38 2D 41 45 38 43 2D 34 34 37 31 2D 39 34 36 32 2D 30 31 43 33 38 45 37 45 32 31 33 43 7D
  • HKEY_USERS\S-1-5-21-[Varies]\Software\WinRAR\Client Hash: 56 B7 B1 DB CD 55 88 45 C0 9C 19 FC 0C 08 D2 B6
  • HKEY_USERS\S-1-5-21-[Varies]\Software\WinRAR\31AC9F8F116B94DA9B66B3AE6E8BF495: 74 72 75 65
  • HKEY_USERS\S-1-5-21-[Varies]\Software\WinRAR\8299E128293DFFF6DA83DD19024A939C: 74 72 75 65

The above registry key values confirm that the system is compromised by PWS variant.
  • HKEY_USERS\S-1-5-[Varies]\Software\Classes\CLSID\{GUID}\InprocServer32\ThreadingModel: "Both"
  • HKEY_USERS\S-1-5-21-[Varies]\Software\Classes\CLSID\{GUID}\InprocServer32\: "%SYSTEMDRIVE%\RECYCLER\S-1-5-21-[Varies]\$698a2431bf10457d451afdf8d202d9b0\n."
  • HKEY_USERS\S-1-5-[Varies]_Classes\CLSID\{GUID}\InprocServer32\ThreadingModel: "Both"
  • HKEY_USERS\S-1-5-21-[Varies]_Classes\CLSID\{GUID}\InprocServer32\: "%SYSTEMDRIVE%\RECYCLER\S-1-5-21-[Removed]\$698a2431bf10457d451afdf8d202d9b0\n."

The above registry key values confirm the Trojan installed rootkit and registers with the compromised system and executes the rootkit upon system boot.

The following are the registry key values modified from the system
  • HKEY_LOCAL_MACHINE \SOFTWARE\Classes\CLSID\{GUID}\InprocServer32\: "%WINDIR%\system32\wbem\fastprox.dll"
  • HKEY_LOCAL_MACHINE \SOFTWARE\Classes\CLSID\{GUID}\InprocServer32\: "%SYSTEMDRIVE%\RECYCLER\S-1-5-18\$8799278523af799c26e02500d72b61fb\n."

The above registry entry confirms that the dropped file registered with the compromised system and gets execute upon system boot.
The following are the Registry keys deleted from the system in order to disables the Windows Firewall and Security center.
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SHAREDACCESS
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SHAREDACCESS\0000
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_SHAREDACCESS\0000\Control
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WSCSVC
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WSCSVC\0000
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\Root\LEGACY_WSCSVC\0000\Control
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\AuthorizedApplications\List
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Setup
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Setup\InterfacesUnfirewalledAtUpdate
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SharedAccess\Enum
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc\Parameters
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc\Security
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc\Enum


-----------------Updated on 11 Feb 2013----------------------

Aliases –

Kaspersky    -    UDS:DangerousObject.Multi.Generic
Jiangmin    -    TrojanDownloader.Java.at
Sweep        -    Mal/JavaJar-B
Trend        -    TROJ_GEN.FCBHZJ8

“Exploit-CVE2012-0507” is an unspecified vulnerability in the Java Runtime Environment component in Oracle Java SE JDK and JRE 5(update 33),6(Update 30) and 7(update 2) and earlier updates allows remote untrusted Java Web Start applications and untrusted Java applets to affect confidentiality, integrity, and availability via unknown vectors related to Scripting.

“Exploit-CVE2012-0507” is exploits the vulnerability present in the AtomicReference Array to bypass the java sandbox mechanism which permits Java to download and execute malware. The Applet typically contains code that consumes a URL Name (also a part of the Applet) which hosts the malware.

This vulnerability is triggered due to the way error objects are handled by the vulnerable JavaScript engine. Normally Java Script Engines ensure that it executes only trusted code within the Java Runtime Environment as opposed to untrusted Applet code.

The attacker crafts the class file with the serialized object data where it will trigger the vulnerability by deserializing the object array. The Vulnerability triggering class file is called by another class file which acts as a loader. Once it is exploited the loader class file will call another class file which will download the payload and execute it.

The exploit first creates an error object which the vulnerable Java Script Engine cannot handle, and then it executes a script that disables the Java Security Manager using the "toString" method. It then throws an Exception and proceeds further and calls with the malicious class file to execute the arbitrary code.

In the wild, it can be found as a Java archive. The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.
 
The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.

The JAR file contains class files which triggers the Vulnerability
  • test.class (Exploit and Vulnerability triggering class file)
  • mac.class (Class Loader)
  • hw.class (Applet class) 

Upon execution, the Trojan attempts to affects the vulnerability in Java Runtime Environment (JRE).

The arbitrary file is a URL is to create a java.net.URL object, then call its openStream() method. The method handles the details of creating the connection, issuing an HTTP GET request, and retrieving the response data.


------Updated on Dec 20, 2012-----

Aliases

  • Drweb      -    Exploit.Java.413
  • Fortinet    -    W32/JavaBz.LF!tr
  • Ikarus       -    Exploit.Java.CVE-2012
  • Microsoft  -    Exploit:Java/CVE-2012-0507.BHP


Characteristics 

“Exploit-CVE2012-0507” is exploits the vulnerability present in the AtomicReference Array to bypass the java sandbox mechanism. The attacker crafts the class file with the serialized object data where it will trigger the vulnerability by deserializing the object array. The Vulnerability triggering class file is called by another class file which acts as a loader. Once it is exploited the loader class file will call another class file which will download the payload and execute it.

This vulnerability is triggered due to the way error objects are handled by the vulnerable JavaScript engine. Normally Java Script Engines ensure that it executes only trusted code within the Java Runtime Environment as opposed to untrusted Applet code.

The exploit first creates an error object which the vulnerable Java Script Engine cannot handle, and then it executes a script that disables the Java Security Manager using the "toString" method. It then throws an Exception and proceeds further and calls with the malicious class file to execute the arbitrary code.

In the wild, it can be found as a Java archive. The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.
 
The malicious HTML passes the encrypted URL of the file to download and execute as the parameter x to the applet.

The JAR file contains class files which triggers the Vulnerability
  • test.class (Exploit and Vulnerability triggering class file)
  • mac.class (Class Loader)
  • hw.class (Applet class)

Upon execution, the Trojan attempts to affects the vulnerability in Java Runtime Environment (JRE).
The arbitrary file is a URL is to create a java.net.URL object, then call its openStream() method. The method handles the details of creating the connection, issuing an HTTP GET request, and retrieving the response data.

The class file exploits the vulnerability present in the AtomicReference Array to bypass the java sandbox mechanism. The attacker crafts the class file with the serialized object data where it will trigger the vulnerability by deserializing the object array. The Vulnerability triggering class file is called by another class file which acts as a loader. Once it is exploited the loader class file will call another class file which will download the payload and execute it. So in our case,

    • Fon.class (Vulnerability triggering class file)
    • Fox.class (Class Loader)
    • Gut .class (for downloading the payload file)

In some cases the payload is an encrypted malware file which will be installed upon successfull exploitation. The encypted malware is embedded in the jar file as a resource. the following name have been observed:

  • KJOTCNXU
  • CMQSQVRW

current dropped files when decrypted are detected as BackDoor-FEQ.
   

All Users:
Use current engine and DAT files for detection and removal.

Modifications made to the system Registry and/or INI files for the purposes of hooking system startup, will be successfully removed if cleaning with the recommended engine and DAT combination (or higher).