FYI...
-
http://community.web...xploit-kit.aspx
* Update 2012/02/06: After obtaining access to logs and PHP files from compromised Web servers, further analysis indicates that most of the compromised Web sites were running older versions of WordPress, but they were not all running 3.2.1. The attackers’ exact point of entry is uncertain. At first, we suspected vulnerable WordPress plugins, because a subset of analyzed sites were running vulnerable versions of the same WordPress plugins. Now that we have access to data from several compromised Web servers, the logs show us that, in some cases, the point of entry was compromised FTP credentials. In several instances, once attackers had access, they scanned WordPress directories and injected specific files (e.g., index.php and wp-blog-header.php) with malicious PHP code.
___
WordPress exploit in-the-wild for v3.2.1 sites ...
-
http://community.web...xploit-kit.aspx
30 Jan 2012 - "... site was compromised because it was running an old version of Wordpress (3.2.1) that is vulnerable to
publicly available exploits... more interesting is the redirection chain and resulting exploit site... From our analysis the number of infections is growing steadily (100+)... The Java exploit being served is CVE-2011-3544* (Oracle Java Applet Rhino Script Engine Remote Code Execution), which most Exploit Kits adopted in December 2011 because it is cross-platform and exploits a design flaw. Normally, kits use a variety of exploits... regardless of what OS or browser we used for testing, this Exploit Kit attempted to exploit ONLY our Java Runtime Environment (JRE).
It did not attempt -any- other exploit... Websense... has found 100+ compromised Web sites, all with similar infection characteristics. The compromised Web sites all share these traits:
>
Running WordPress 3.2.1
>
Force a drive by download via iframe to the same
malicious set of domains hosting a PHP Web page in the form of: [subdomain]
.osa .pl/showthread.php?t=.*
>
Attempt exploitation using CVE-2011-3544
If exploitation is successful, ( the
Tdss rootkit will be installed ) on the user's machine.
If you're running WordPress 3.2.1, we recommend that:
You upgrade to the latest stable version of WordPress**.
Check the source code of all your Web pages to see if you've been infected (see the code above). If you have been infected, be sure to upgrade WordPress while simultaneously removing the injected code so that your Web pages aren't simply being reinfected after being cleaned.
**
https://wordpress.org/download/
January 3, 2012 - "The latest stable release of WordPress (Version 3.3.1) is available..."
Massive Compromise of
WordPress-based sites...
-
http://labs.m86secur...siv...-fine’/
Jan 30, 2012 - "... hundreds of websites, based on WordPress 3.2.1... The attacker uploaded an HTML page to the standard Uploads folder and that page redirects the user to the
Phoenix Exploit Kit... logs show that users from at least -400- compromised sites were -redirected- to
Phoenix exploit pages..."
___
SiteCheck scanner
-
http://sucuri.net/global
___
*
http://web.nvd.nist....d=CVE-2011-3544
Last revised: 01/27/2012
"... vulnerability in the Java Runtime Environment component in Oracle Java SE JDK and JRE 7 and 6 Update 27
and earlier..."
CVSS v2 Base Score:
10.0 (HIGH)
Latest Java versions available here:
Downloads:
http://www.oracle.co...oads/index.html
JRE
6u30:
http://www.oracle.co...ad-1377142.html
JRE
7u2:
http://www.oracle.co...ad-1377135.html
___
-
https://www.virustot...0b73e/analysis/
File name:
file-3486436_jar
Detection ratio:
12/41
Analysis date: 2012-01-31
-
https://www.virustot...12483/analysis/
File name:
39301c3e4ae8ed0e4faf0c3c18cf54a0
Detection ratio:
10/43
Analysis date: 2012-01-30
-
https://www.virustot...sis/1327739797/
File name:
oleda0.027112496150291654.exe
Detection ratio:
9/43
Analysis date: 2012-01-28
Edited by AplusWebMaster, 07 February 2012 - 07:06 AM.