Trendmicro Vulnerability Protection vulnerabilities

5 vulnerabilities

Known vulnerabilities in Trendmicro Vulnerability Protection, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

8.1CVE-2020-15605trend microtrend micro vulnerability protection+2
EPSS score
2.61%
If LDAP authentication is enabled, an LDAP authentication bypass vulnerability in Trend Micro Vulnerability Protection 2.0 SP2 could allow an unauthenticated attacker with prior knowledge of the targeted organization to bypass manager authentication. Enabling multi-factor authentication prevents this attack. Installations using manager native authentication or SAML authentication are not impacted by this vulnerability.8.1CVE-2020-15601trend microtrend micro deep security+2
EPSS score
2.61%
If LDAP authentication is enabled, an LDAP authentication bypass vulnerability in Trend Micro Deep Security 10.x-12.x could allow an unauthenticated attacker with prior knowledge of the targeted organization to bypass manager authentication. Enabling multi-factor authentication prevents this attack. Installations using manager native authentication or SAML authentication are not impacted by this vulnerability.7.2CVE-2020-8602trend microtrend micro deep security+3
EPSS score
4.01%
A vulnerability in the management consoles of Trend Micro Deep Security 10.0-12.0 and Trend Micro Vulnerability Protection 2.0 SP2 may allow an authenticated attacker with full control privileges to bypass file integrity checks, leading to remote code execution.7.8CVE-2020-8601trend microtrend micro vulnerability protection+1
EPSS score
0.40%
Trend Micro Vulnerability Protection 2.0 is affected by a vulnerability that could allow an attack to use the product installer to load other DLL files located in the same directory.4.9CVE-2019-9488trend microtrend micro deep security+3
EPSS score
1.23%
Trend Micro Deep Security Manager (10.x, 11.x) and Vulnerability Protection (2.0) are vulnerable to a XML External Entity Attack. However, for the attack to be possible, the attacker must have root/admin access to a protected host which is authorized to communicate with the Deep Security Manager (DSM).