Exploit kits attack vector – mid
Vulnerabilities mentionedAll →
| CVE | Vulnerability | CVSS | EPSS | Flags | Affected | Exposure | Published |
|---|---|---|---|---|---|---|---|
| CVE-2007-5659 | Buffer Overflow in Adobe Acrobat and Reader via Malicious PDF JavaScript Adobe Acrobat and Reader contain a buffer overflow (CWE-119) in their handling of arguments passed to JavaScript methods when rendering PDF files. An attacker triggers the flaw by convincing a user to open a crafted PDF whose embedded JavaScript calls methods with overly long arguments, and no user privileges beyond viewing the file are required. Successful exploitation allows a remote attacker to execute arbitrary code in the context of the user running Acrobat or Reader. Anyone running the affected Acrobat or Reader versions (specific version ranges are not provided in the source data) is affected, with Adobe Reader historically being one of the most widely deployed desktop applications. CISA added the vulnerability to the Known Exploited Vulnerabilities catalog on 2022-06-08, confirming exploitation in the wild, and EPSS assigns a 94% probability of exploitation within 30 days (100th percentile); no public proof-of-concept is known and ransomware use is unknown. Do: Apply updates per vendor instructions by upgrading Acrobat and Reader to the patched releases Adobe made available for your version line, and audit the estate for legacy, unpatched Acrobat/Reader installs given the 2022 KEV listing. As an interim mitigation, disable or restrict JavaScript in the Acrobat/Reader preferences and treat PDFs from untrusted sources (email attachments, drive-by download sites, exploit-kit delivery channels) with caution. | — | 94% | KEV |
| masshundreds of millions of users/installations historically (Adobe Reader/Acrobat is among the most widely deployed desktop PDF viewers); current unpatched… | |
| CVE-2008-2992 | Adobe Acrobat and Reader JavaScript Input Validation Flaw Enables Remote Code Execution Adobe Acrobat and Reader contain an input validation flaw (CWE-119, memory corruption) in a JavaScript method — historically the util.printf() JavaScript function — that fails to safely handle crafted arguments. An attacker triggers the flaw by getting a user to open a specially crafted PDF containing malicious JavaScript, which can corrupt memory and allow code execution on the victim's machine. Successful exploitation yields remote code execution with the privileges of the logged-in user, typically used to deliver malware; the related headlines indicate this flaw was folded into exploit kits and spam-driven malware campaigns of the era. Anyone running a vulnerable version of Adobe Acrobat or Reader (specific version ranges were not provided in the source data) with PDF JavaScript enabled is affected. Exploitation is confirmed in the wild: the flaw was added to CISA KEV on 2022-03-03 with known ransomware use, and EPSS assigns it a 98.5% probability of exploitation within 30 days. Do: Apply updated versions of Acrobat and Reader per Adobe's instructions, as required by the CISA KEV listing. As an interim mitigation, disable or restrict JavaScript in Acrobat/Reader preferences (a JavaScript blocklist/allowlist approach, consistent with Adobe's JavaScript Blocklist Framework), and caution users against opening unsolicited PDFs, since exploitation has occurred via exploit kits, spam campaigns, and ransomware delivery. Check endpoints for unpatched Acrobat/Reader installs and confirm remediation against the CISA KEV deadline. | — | 98% | KEV ransomware |
| massHundreds of millions of desktop users (an estimate | |
| CVE-2009-0927 | Stack-Based Buffer Overflow in Adobe Reader and Acrobat Enables Remote Code Execution CVE-2009-0927 is a stack-based buffer overflow (improper input validation, CWE-20) in Adobe Reader and Adobe Acrobat that allows remote attackers to execute arbitrary code on the victim's system. The flaw is triggered when the PDF handling code in these products processes malicious input, typically via a specially crafted PDF document delivered through email, the web, or exploit kits. Successful exploitation gives an attacker the ability to run arbitrary code, generally with the privileges of the user running the PDF application. Any user or endpoint running an affected version of Adobe Reader or Acrobat is exposed, and given the near-universal deployment of these PDF tools the potential population is very large. The vulnerability is listed in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-25) with a required action to apply vendor updates, and EPSS assigns a 96.6% probability of exploitation within 30 days, though no public proof-of-concept is known. Do: Apply updates per vendor instructions: upgrade all affected Adobe Reader and Acrobat installations to a patched release as required by the CISA KEV listing. As an interim mitigation, disable or restrict JavaScript in PDF files (the Acrobat JavaScript blocklist framework introduced around this period addresses this vector) and block PDFs from untrusted sources. Inventory endpoints for outdated Reader/Acrobat versions, prioritizing systems that open PDFs from email and the web. | — | 97% | KEV |
| masshundreds of millions of users (Adobe Reader was the dominant PDF viewer on desktops during the exploitation period) | |
| CVE-2010-0840 | Unspecified Remote Vulnerability in Oracle Java Runtime Environment (JRE) CVE-2010-0840 is an unspecified vulnerability in the Java Runtime Environment (JRE) component of Oracle Java SE that allows remote attackers to affect confidentiality, integrity, and availability through vectors Oracle did not publicly detail. Because the advisory withheld technical specifics, the exact trigger is undocumented, but the flaw is remotely exploitable, and the era's threat reporting (2011 exploit-kit and Java malware headlines) is consistent with drive-by exploitation of Java clients. A successful attacker gains the ability to compromise the confidentiality, integrity, or availability of the affected system, and Java flaws of this period were commonly leveraged to install malware such as bots. Any organization or end user running the affected JRE releases — whether the browser Java plug-in on desktops or server-side Java — is exposed, making the affected population extremely broad. The flaw is listed in CISA's Known Exploited Vulnerabilities catalog (added 2022-05-25), EPSS assigns it a 96.3% probability of exploitation in the next 30 days, and no public proof-of-concept is known. Do: Apply the Oracle Java SE updates specified by the vendor as required by CISA's KEV listing, and remove or disable obsolete or unsupported JRE versions, especially the browser Java plug-in where it is no longer needed. Prioritize internet-exposed and end-user systems, check for lingering legacy Java applets in use, and note that remediation is mandatory for federal agencies under the KEV program. | — | 96% | KEV |
| masshundreds of millions of JRE installations across desktops and servers |
Full article770 words · extracted from securelist.com · click to collapse
It is very interesting to see how short the lifespan of an exploit kit is. Some kits that were once popular and infected thousands of users are no longer being used. Even more interesting is the fact that some old kits make a comeback rearmed with fresh new exploits and reach the top of the rankings in serving malware.
However, the most interesting area of study is how current exploits are used and their targets.
2010
In order to get some perspective, let?s start by analyzing the situation in 2010. The most common exploit kits last year were:
- Phoenix
- Eleonore
- Neosploit
- YESExploitKit
- SEOSploitPack
However, by the end of 2010 there was a rapid decline in the use of Phoenix and an increase in the number of malicious servers serving NeoSploit.
By analyzing the vulnerabilities targeted by these exploit kits, we can infer the main attack vector:

The main point here is not the static picture but the dynamic one. In this case, Java vulnerabilities managed to climb to 3rd place in just one year. 40% of all new exploits used by the top five kits in 2010 targeted Java. According to my colleague Dan Guido, 11 out of the 15 top kits included at least one Java exploit and seven out of the top 15 kits included more than one.
Let?s contrast this information with some more data. According to Microsoft Malware protection center, last year there was a peak in Java exploitation attempts:

Source: arstechnica.com/business/news
Our own records point to a similar situation. Here you can see the creation of Java-related signatures in response to these detected threats:
These exploitation attempts were detected in our customer base as well:
The question is: why Java? I have been pondering this for some time, but the answer came after attending Dino Dai Zovi?s keynote presentation at SOURCE Conference. It was so obvious! The answer is that Java exploits are the easiest way to bypass OS security countermeasures. An image is worth a thousand words in this case:
2011
What is the situation so far this year? Has anything changed? Some things have, namely the top exploit kits for the first half of the year:
| 2010 | 2011 |
| Phoenix | BlackHole |
| Eleonore | NeoSploit |
| NeoSploit | Phoenix |
| YESExploitKit | Incoginto |
| SEOSploitPack | Eleonore |
Two new players have emerged: BlackHole and Incognito. Let?s see what they target.
BlackHole:
- CVE-2010-1885 HCP
- CVE-2010-1423 Java Deployment Toolkit insufficient argument validation
- CVE-2010-0886 Java Unspecified vulnerability in the Java Deployment Toolkit component in Oracle Java SE
- CVE-2010-0842 Java JRE MixerSequencer Invalid Array Index Remote Code Execution Vulnerability
- CVE-2010-0840 Java trusted Methods Chaining Remote Code Execution Vulnerability
- CVE-2009-1671 Java buffer overflows in the Deployment Toolkit ActiveX control in deploytk.dll
- CVE-2009-0927 Adobe Reader Collab GetIcon
- CVE-2008-2992 Adobe Reader util.printf
- CVE-2007-5659 Adobe Reader CollectEmailInfo
- CVE-2006-0003 IE MDAC
Basically, we have here the usual things that almost all kits include, the only difference being the first two vulnerabilities – CVE-2010-1885 and CVE-2010-1423. The latter of these two targets Java.
What about Incognito? Here is the corresponding list:
- CVE-2010-1885 HCP
- CVE-2010-1423 Java Deployment Toolkit insufficient argument validation
- CVE-2010-0886 Java Unspecified vulnerability in the Java Deployment Toolkit component in Oracle Java SE
- CVE-2010-0842 Java JRE MixerSequencer Invalid Array Index Remote Code Execution Vulnerability
- CVE-2009-0927 Adobe Reader Collab GetIcon
- CVE-2008-2992 Adobe Reader util.printf
- CVE-2007-5659/2008-0655 Adobe Reader CollectEmailInfo
- CVE-2006-4704 Microsoft Visual Studio 2005 WMI Object Broker Remote Code Execution Vulnerability
- CVE-2004-0549 ShowModalDialog method and modifying the location to execute code
Apart from the last two (CVE-2006-4704 and CVE-2004-0549), this list is exactly the same as the one for BlackHole.
So, what is the verdict? These two kits are not adding anything new to the landscape and are still using the same exploits and targeting Java.
After this review, there are a few conclusions we can reach:
- The reason that Java is becoming the most targeted platform is because it is the easiest way to avoid the main OS protection mechanisms.
- The changes in the Top 5 most widespread exploit kits are not related to the exploits being used.
- There is no need to use valuable zero-days while older vulnerabilities continue to be exploited on unpatched machines.
Cybercriminals are showing once again how much they care about their return on investment and go just as far as they need to stay one step ahead of protection mechanisms. In this case, another well known claim can be applied: security is as strong as the weakest link – Java is the weakest link in this case.
Here at Kaspersky Lab, we will continue to study the landscape for the rest of the year and will closely follow any interesting changes to the attack vectors.
Text extracted automatically; images, tables and formatting may be missing. Original: https://securelist.com/exploit-kits-attack-vector-mid-year-update/35986/