Filtered by vendor Pritunl
Subscribe
Total
6 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2022-25372 | 2 Microsoft, Pritunl | 2 Windows, Pritunl-client-electron | 2024-11-21 | 7.2 HIGH | 7.8 HIGH |
Pritunl Client through 1.2.3019.52 on Windows allows local privilege escalation, related to an ACL entry for CREATOR OWNER in platform_windows.go. | |||||
CVE-2020-27519 | 1 Pritunl | 1 Pritunl-client-electron | 2024-11-21 | 7.2 HIGH | 7.8 HIGH |
Pritunl Client v1.2.2550.20 contains a local privilege escalation vulnerability in the pritunl-service component. The attack vector is: malicious openvpn config. A local attacker could leverage the log and log-append along with log injection to create or append to privileged script files and execute code as root/SYSTEM. | |||||
CVE-2020-25989 | 1 Pritunl | 1 Pritunl-client-electron | 2024-11-21 | 7.2 HIGH | 7.8 HIGH |
Privilege escalation via arbitrary file write in pritunl electron client 1.0.1116.6 through v1.2.2550.20. Successful exploitation of the issue may allow an attacker to execute code on the effected system with root privileges. | |||||
CVE-2020-25200 | 1 Pritunl | 1 Pritunl | 2024-11-21 | 5.0 MEDIUM | 5.3 MEDIUM |
Pritunl 1.29.2145.25 allows attackers to enumerate valid VPN usernames via a series of /auth/session login attempts. Initially, the server will return error 401. However, if the username is valid, then after 20 login attempts, the server will start responding with error 400. Invalid usernames will receive error 401 indefinitely. Note: This has been disputed by the vendor as not a vulnerability. They argue that this is an intended design | |||||
CVE-2016-7064 | 1 Pritunl | 1 Pritunl-client | 2024-11-21 | 5.0 MEDIUM | 7.5 HIGH |
A flaw was found in pritunl-client before version 1.0.1116.6. A lack of signature verification leads to sensitive information leakage | |||||
CVE-2016-7063 | 1 Pritunl | 1 Pritunl-client | 2024-11-21 | 7.5 HIGH | 9.8 CRITICAL |
A flaw was found in pritunl-client before version 1.0.1116.6. Arbitrary write to user specified path may lead to privilege escalation. |