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
Yokogawa CENTUM CS 3000 BKCLogSvr Buffer Overflow Exploit
This module exploits a remote stack-based buffer overflow in Yokogawa CS3000 by sending a malformed packet to the 52302/UDP port.
Yokogawa Centum CS 3000 BKBCopyD Remote Buffer Overflow Exploit
This module exploits a stack based buffer overflow in Yokogawa CENTUM CS 3000 by using its BKBCopyD.exe service. The Yokogawa Centum CS3000 solution uses different services in order to provide all its functionality. The BKBCopyD.exe service, started when running the FCS / Test Function, listens by default on TCP/20111. By sending a specially crafted packet to the port TCP/20111, it it is possible to trigger a stack based buffer overflow which allows execution of arbitrary code with the privileges of the CENTUM user.
A vulnerability has been reported in MyBB, which can be exploited by malicious users to conduct SQL injection attacks. Input passed via the "birthdayprivacy" parameter to inc/datahandlers/user.php is not properly sanitised before being used in SQL queries. This can be exploited to manipulate SQL queries by injecting arbitrary SQL code. Successful exploitation requires a valid user account. The vulnerability is reported in MyBB 1.4.x versions prior to 1.4.7. This modules gives to a normal user, admin privileges.
Exploits / Authentication Weakness / Known Vulnerabilities
Impact
OpenSite Weak Authentication Exploit
This module exploits an authentication vulnerability in OpenSite 2.1. The function init in origin/libs/user.php checks for a matching origin_hash cookie. However, this cookie can be bruteforced in at most 2^32 tries for a known username. Actually, the number of attempts could be significantly reduced knowing that we do not have to check for time in the future, and long past. This works for OpenSite 2.1 and below. It has to be executed against the root directory of OpenSite.
Exploits / Authentication Weakness / Known Vulnerabilities
Impact
Tomcat orderby Cross Site Scripting Exploit
There is a reflected Cross-Site Scripting attack. An attacker able to cause a user to follow a specially crafted malicious link may be able to recover session identifiers or exploit browser vulnerabilities. The orderby parameter is vulnerable to cross-site scripting.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Testlink login Cross Site Scripting Exploit
A cross-site scripting vulnerability is present in TestLink before 1.8.5 allowing remote attackers to inject arbitrary web script or HTML via the req parameter to login.php.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Oracle Business Process Management Cross Site Scripting Exploit
There is a reflected Cross-Site Scripting attack. An attacker able to cause a user to follow a specially crafted malicious link may be able to recover session identifiers or exploit browser vulnerabilities. The template parameter is vulnerable to cross-site scripting.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
OpenEMR pc_category Cross Site Scripting Exploit
OpenEMR fails to sanitize the pc_category parameter in interface/main/calendar/index.php leading to a Cross-Site Scripting vulnerability. This exploit was tested on OpenEMR 4.0.0 but other versions may also be affected.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Moodle phpcoverage_home Cross Site Scripting Exploit
Moodle fails to sanitize the phpcoverage_home parameter in phpcoverage.remote.top.inc.php leading to a Cross-Site Scripting vulnerability.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Moodle blog Cross Site Scripting Exploit
Some parameters were not being properly cleaned on the blog index page, allowing non-persistent cross-site scripting (XSS) attacks. Affects Moodle branch 1.9.x from 1.9.8 and prior and branch 1.8.x from 1.8.13 and prior. This bug exists in the previous and next links on a paginated blog.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
MoinMoin Template Cross Site Scripting Exploit
There is a possible reflected Cross-Site Scripting attack. An attacker able to cause a user to follow a specially crafted malicious link may be able to recover session identifiers or exploit browser vulnerabilities. The template parameter is vulnerable to cross-site scripting. Affects MoinMoin 1.9.2 and prior.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Microsoft Sharepoint Server 2007 Cross Site Scripting Exploit
The vulnerability exists due to failure in the "/_layouts/help.aspx" script to properly sanitize user-supplied input in "cid0" variable. Successful exploitation of this vulnerability could result in a compromise of the application, theft of cookie-based authentication credentials, disclosure or modification of sensitive data.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Jetty Directory Listing Cross Site Scripting Exploit
Jetty versions 6.1.16 and below are vulnerables. A Cross-Site scripting vulnerability has been reported in Jetty. This vulnerability can be induced whenever Jetty displays a web directory listing. Client-side script code can be included in the HTTP response by appending it next to directory listing's path, preceded by a ';' character.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Drupal Forum Cross Site Scripting Exploit
A Cross-Site Scripting (XSS) vulnerability in the Forum module in Drupal 6.x (prior to version 6.13) allows remote attackers to inject arbitrary web scripts or HTML by requesting a specially crafted tid. Forum module must be active in the attacked Drupal
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Bugtracker.net edit_comment Cross Site Scripting Exploit
The application fails to sanitize the bug_id parameter in several pages such as edit_comment and edit_bug, leading to a cross site scripting vulnerability.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Achievo atksearch Cross Site Scripting Exploit
A Reflected Cross Site Scripting vulnerability was found in the atksearch[contractnumber], atksearch_AE_customer[customer] and atksearchmode[contracttype] variables within the 'Organization Contracts' administration page. This is because the application does not properly sanitize the users input. Vulnerable version is = 1.3.4.
Exploits / Cross Site Scripting (XSS) / Known Vulnerabilities
Impact
Wordpress Weak Authentication Exploit
This module exploits an authentication vulnerability in Wordpress 2.5. An attacker, able to register a specially crafted username on a Wordpress 2.5 installation, will also be able to generate authentication cookies for other chosen accounts. This vulnerability exists because it is possible to modify authentication cookies without invalidating the cryptographic integrity protection. The proper way to exploit this vulnerability is to use a Wordpress account which its username starts with the word "admin", for example "admin99".
Exploits / Authentication Weakness / Known Vulnerabilities
Impact
Wordpress Reset Password Exploit
A weakness has been reported in WordPress which can be exploited to bypass certain security restrictions. The weakness is due to a bug within the password reset functionality when verifying the secret key. This can be exploited to reset the password of the first user without a key in the database (usually administrator) without providing the correct secret key.