Exploit development can be an advanced penetration testing skill that takes time to master. Additionally, when on a job, pen testers often don’t have the resources to create a new exploit. Many resort to searching for and using pre-written exploits that have not been tested and must go through the timely effort of quality assurance testing in order to ensure they are secure and effective.
Core Impact users can save time by finding all the up-to-date exploits they need in one place. We provide a robust library of exploits designed to enable pen testers to safely and efficiently conduct successful penetration tests. Witten by our own internal team, you can trust they have been thoroughly tested and validated by our experts.
The universe of vulnerabilities is huge and not all of them represent the same risk for the customers. Vulnerabilities do not all have the same level of criticality. Some may be easily exploitable by a low-level user, while others may not be exploitable at all. To increase the efficiency of the attacks and the quality of the exploits provided, the Core Impact team has developed selection criteria to prioritize its analysis and implementation. We determine which exploits warrant creation based on the following questions:
What are the most critical attacks from the attacker’s perspective?
What new vulnerabilities are more likely to be exploited in real attacks?
What exploits are the most valuable for Core Impact?
Once an exploit is approved, its priority order considers the following variables:
Vulnerability Properties: CVE, disclosure date, access mechanism and privileges needed.
Target Environment Setup: OS, application prevalence, version and special configurations needed.
Value Provided to Core Impact: Customer request, usage in multiple attacks, allows the installation of an agent, etc.
Technical Cost vs. Benefit: An analysis weighing the resources needed to build an exploit with the internal and external knowledge gained in its creation.
Each one of these variables has a different weight and provides a ranking of the potential exploits to be developed. Following those criteria, the top of the list would contain, for example, a vulnerability on Windows (most popular OS) that can be exploited remotely, without authentication and that provides super user privileges.
Correspondingly, a vulnerability on an application that is rarely installed, needs special configurations, and requires User Interaction, would be at the bottom.
Stay Informed of New Core Certified Exploits
Subscribe to receive regular email updates on new exploits available for Core Impact
Browse the Core Certified Exploit Library
We provide pen testers with real-time updates for a wide range of exploits for different platforms, operating systems, and applications.
Search our continuously growing library to discover an exploit that will allow you to gain and retain access on the target host or application.
Title
Description
Date Added
CVE Link
Exploit Platform
Exploit Type
Product Name
W3C Amaya Web Browser INPUT Tag Buffer Overflow Exploit
Multiple stack buffer overflow vulnerabilities have been discovered in Amaya, which can be exploited by malicious people to compromise a users system. This module runs a web server waiting for vulnerable clients (W3C Amaya Web Browser) to connect to it. When the client connects, it will try to install an agent by exploiting this vulnerability.
Watermark Master is prone to a buffer overflow vulnerability when handling WCF files. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.
The vulnerability is a buffer overflow and exists within the Webgate WESP SDK WESPMonitor Module ActiveX control's LoadLibrary property. This module runs a web server waiting for vulnerable clients (Internet Explorer 6, 7, 8 to connect to it.
By properly setting the ProjectURL property, it is possible for an attacker to download an arbitrary dll file from a remote location and run the code in the dll in the context of the target process. This module runs a web server waiting for vulnerable clients (Internet Explorer) to connect to it. When the client connects, it will try to install an agent by exploiting this vulnerability.
A vulnerability exists within the WkWin32.dll module when processing the DisplayMessageDialog() method. This module runs a web server waiting for vulnerable clients (Internet Explorer 6 and 7) to connect to it. When the client connects, it will try to install an agent by exploiting this vulnerability.
Windows
Exploits / Client Side
Impact
Winamp Computer Name Handling Buffer Overflow Exploit
This module runs a web server waiting for vulnerable clients (Internet Explorer) to connect to it. When the client connects, it will try to install an agent by exploiting a vulnerability in the way .PLS (Play List) files are handled by Winamp 5.12. When Outlook Express is used as mail user agent, Internet Explorer can be exploited through sending the target an e-mail that contains a link to the specially designed HTML page that triggers the attack. Also, this module can drop a specially crafted PLS file in a local folder of the user's choice.
Winamp is prone to a vulnerability that may allow execution of dwmapi.dll if this dll is located in the same folder than a .CDA file. The attacker must entice a victim into opening a specially crafted .CDA file. This file and the associated binary may be delivered to a user through remote WebDAV shares. An attacker may exploit this issue to execute arbitrary code.
Windows
Exploits / Client Side
Impact
Winamp gen_ff DLL Buffer Overflow Exploit
A stack-based buffer overflow in Winamp allows an attacker to execute arbitrary code via crafted .MAKI file. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.
This module exploits a heap-based buffer overflow in IN_MOD.DLL (aka the Module Decoder Plug-in) in order to install an agent via crafted samples in an Impulse Tracker file. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.
Winamp is prone to a buffer-overflow vulnerability that occurs because it fails to perform adequate boundary checks on user-supplied data via a crafted .MID file. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.
A integer overflow in Winamp allows an attacker to execute arbitrary code via crafted .MP4 file. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.
Windows
Exploits / Client Side
Impact
Winamp Ultravox Streaming Buffer Overflow Exploit
This module exploits a vulnerability in Winamp Player when parsing the Ultravox Streaming metadata. This module runs a web server waiting for vulnerable clients (Internet Explorer, Opera or Mozilla Firefox) to connect to it. When the client connects, it will try to install an agent by exploiting this vulnerability.
A remote code execution vulnerability exists in the way that Windows handles cursor, animated cursor, and icon formats. An attacker could try to exploit the vulnerability by constructing a malicious cursor or icon file that could potentially allow remote code execution if a user visited a malicious Web site or viewed a specially crafted e-mail message (MS07-017)
This module exploits a buffer overflow in the Microsoft Internet Explorer via a Stack-based buffer overflow in Microsoft Internet Explorer allowing remote attackers to execute arbitrary code via a long fill parameter within a rect tag in a Vector Markup Language (VML) file.
This module exploits a buffer overflow in the Microsoft Internet Explorer when calling the 'setSlice' method of the WebViewFolderIcon.WebViewFolderIcon.1 ActiveX object with the first parameter set to 0x7ffffffe. This causes an invalid memory copy and may result in arbitrary code execution and/or a loss of availability for the browser.
This module exploits a buffer overflow in the Microsoft Color Management Module via an jpeg image with crafted ICC profile format tags and installs an agent.
The vulnerability is on IDF entry of tif/tiff image format, the Kodak Image Viewer reserves a insufficient buffer in the stack for write the entry to it. When Kodak Image Viewer opens the file, it produces a stack overflow and install an agent.
Windows Live Mail is prone to a vulnerability that may allow the execution of any library file named dwmapi.dll, if this dll is located in the same folder as an .EML file. The attacker must entice a victim into opening a specially crafted .EML file. This file and the associated binary may be delivered to a user through remote WebDAV shares. An attacker may exploit this issue to execute arbitrary code.
Windows
Exploits / Client Side
Impact
Microsoft Windows Media Encoder DLL Hijacking (MS10-094)
Windows Media Encoder is prone to a vulnerability that may allow the execution of any library file named wmerrorENU.dll, if this dll is located in the same folder as a .PRX file. The attacker must entice a victim into opening a specially crafted .PRX file. This file and the associated binary may be delivered to a user through remote WebDAV shares. An attacker may exploit this issue to execute arbitrary code.
WinHex is prone to a vulnerability that may allow the execution of any library file named hash.dll, if this dll is located in the same folder as a .WHX file. The attacker must entice a victim into opening a specially crafted .WHX file. This file and the associated binary may be delivered to a user through remote WebDAV shares. An attacker may exploit this issue to execute arbitrary code.
Windows
Exploits / Client Side
Impact
WinHlp32 exploit
This module exploits a vulnerability located in the parameter parser of the Microsoft Windows WinHLP facility. This facility is used by the Microsoft Internet Explorer web browser.
The vulnerability is caused due to boundary errors in lzh.fmt within the processing of LHA archives. This can be exploited to cause a stack-based buffer overflow when a specially crafted file with an overly long filename is opened.
The file names showed in WinRAR when opening a ZIP file come from the central directory, but the file names used to extract and open contents come from the Local File Header. This module runs a malicious web server on the Core Impact Console and waits for an unsuspecting user to trigger the exploit by connecting to it.