This module exploits a remote code execution vulnerability that exists in Exchange Reporter Plus <= 5310, caused by execution of bcp.exe file inside ADSHACluster servlet.
This is a kernel exploit for counterfeit grsec kernels such as KSPP and linux-hardened. It allows an attacker to gain root privileges by leveraging a vulnerability in the Linux kernel.
This is an exploit for PHP Homepage M V.1.0 galerie.php. It allows an attacker to execute arbitrary code on the target system. The exploit works when magic_quotes_gpc is turned off.
Dicoogle PACS 2.5.0 is vulnerable to local file inclusion, allowing an attacker to read arbitrary files that the web user has access to. Admin credentials are not required. The 'UID' parameter via GET is vulnerable.
IBM QRadar SIEM has three vulnerabilities in the Forensics web application that when chained together allow an attacker to achieve unauthenticated remote code execution. The first stage bypasses authentication by fixating session cookies. The second stage uses those authenticated sessions cookies to write a file to disk and execute that file as the "nobody" user. The third and final stage occurs when the file executed as "nobody" writes an entry into the database that causes QRadar to execute a shell script controlled by the attacker as root within the next minute. Details about these vulnerabilities can be found in the advisories listed in References. The Forensics web application is disabled in QRadar Community Edition, but the code still works, so these vulnerabilities can be exploited in all flavours of QRadar. This module was tested with IBM QRadar CE 7.3.0 and 7.3.1. IBM has confirmed versions up to 7.2.8 patch 12 and 7.3.1 patch 3 are vulnerable. Due to payload constraints, this module only runs a generic/shell_reverse_tcp payload.
Through analyzing the Captcha function implemented in the DIR-601 (2.02NA firmware), a HTTP request was found responsible for the handoff to client-side code. Inspecting the HTTP requests, it was identified that a parameter named ‘table_name’ is used to instruct the back-end application which content to return. By abusing this request, it was found possible to retrieve sensitive information relating to the device configuration and administrative credentials. It is possible to modify the HTTP POST to my_cgi.cgi and include as table_name references to retrieve the administrative credentials, wireless ssid, and pre-shared key where applicable. Enumerating the naming conventions within the client-side code, it was determined that a number of potentially sensitive parameters/tables exist in the back-end environment which provide significant value if retrieved, four of these include: - Admin_user - Wireless_settings - Wireless_security - Wireless_wpa_settings
This vulnerability allows for local file inclusion and cross-site scripting (XSS) attacks. The first vulnerability can be exploited by accessing the backend/admin-functions.php file with a malicious ss_uri parameter. The second vulnerability can be exploited by accessing the pjirc/css.php or browse.php files with a malicious color or cat parameter respectively. These vulnerabilities can be used to execute arbitrary code or steal sensitive information from the affected system.
This exploit allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted Yahoo Messenger V5.5 request.
The WolfSight CMS 3.2 is vulnerable to SQL Injection. An attacker can exploit this vulnerability to execute arbitrary SQL commands and gain unauthorized access to the database.
This exploit allows an attacker to execute arbitrary code remotely on a Gitea 1.4.0 server without authentication. The attacker can create a fake OID for the app.ini file and trigger the execution of arbitrary commands.