Pulse Secure Client 9.0R1 and 5.3RX before 5.3R5, when configured to authenticate VPN users during Windows Logon, can allow attackers to bypass Windows authentication and execute commands on the system with the privileges of Pulse Secure Client. The attacker must interrupt the clients network connectivity, and trigger a connection to a crafted proxy server with an invalid SSL certificate that allows certification-manager access, leading to the ability to browse local files and execute local programs.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Pulse_secure_desktop | Pulsesecure | 5.3r1.0 (including) | 5.3r1.0 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r1.1 (including) | 5.3r1.1 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r2.0 (including) | 5.3r2.0 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r3.0 (including) | 5.3r3.0 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r4.0 (including) | 5.3r4.0 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r4.1 (including) | 5.3r4.1 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3r4.2 (including) | 5.3r4.2 (including) |
Pulse_secure_desktop | Pulsesecure | 5.3rx (including) | 5.3rx (including) |
Pulse_secure_desktop | Pulsesecure | 9.0r1.0 (including) | 9.0r1.0 (including) |