HynekPetrak

7 exploits Active since Apr 2017
CVE-2020-3992 NOMISEC CRITICAL SCANNER
VMware ESXi < 7.0.1-0.0.16850804, < 6.7 ESXi670-202010401-SG, < 6.5 ESXi650-202010401-SG - Use-After-Free in OpenSLP
OpenSLP as used in VMware ESXi (7.0 before ESXi_7.0.1-0.0.16850804, 6.7 before ESXi670-202010401-SG, 6.5 before ESXi650-202010401-SG) has a use-after-free issue. A malicious actor residing in the management network who has access to port 427 on an ESXi machine may be able to trigger a use-after-free in the OpenSLP service resulting in remote code execution.
49 stars
CVSS 9.8
CVE-2019-5544 NOMISEC CRITICAL SCANNER
VMware Horizon DaaS 8.0.0-8.9.9 - Heap Overflow via OpenSLP
OpenSLP as used in ESXi and the Horizon DaaS appliances has a heap overwrite issue. VMware has evaluated the severity of this issue to be in the Critical severity range with a maximum CVSSv3 base score of 9.8.
49 stars
CVSS 9.8
CVE-2022-23305 NOMISEC CRITICAL SCANNER
Apache Log4j 1.2.x - SQL Injection via JDBCAppender Message Converter
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
39 stars
CVSS 9.8
CVE-2021-44228 NOMISEC CRITICAL SCANNER
Log4Shell HTTP Header Injection
Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.
39 stars
CVSS 10.0
CVE-2019-17571 NOMISEC CRITICAL SCANNER
Apache Log4j <= 1.2.17 - Deserialization of Untrusted Data via SocketServer
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
39 stars
CVSS 9.8
CVE-2017-5645 NOMISEC CRITICAL SCANNER
Apache Log4j 2.0-2.8.1 - Remote Code Execution via Untrusted Data Deserialization
In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.
39 stars
CVSS 9.8
CVE-2019-0708 NOMISEC CRITICAL SCANNER
CVE-2019-0708 BlueKeep RDP Remote Windows Kernel Use After Free
A remote code execution vulnerability exists in Remote Desktop Services formerly known as Terminal Services when an unauthenticated attacker connects to the target system using RDP and sends specially crafted requests, aka 'Remote Desktop Services Remote Code Execution Vulnerability'.
27 stars
CVSS 9.8