CVSS: 9.3EPSS: 0%CPEs: 2EXPL: 0CVE-2017-17023
https://notcve.org/view.php?id=CVE-2017-17023
The Sophos UTM VPN endpoint interacts with client software provided by NPC Engineering (www.ncp-e.com). The affected client software, "Sophos IPSec Client" 11.04 is a rebranded version of NCP "Secure Entry Client" 10.11 r32792. A vulnerability in the software update feature of the VPN client allows a man-in-the-middle (MITM) or man-on-the-side (MOTS) attacker to execute arbitrary, malicious software on a target user's computer. This is related to SIC_V11.04-64.exe (Sophos), NCP_EntryCl_Windows_x86_1004_31799.exe (NCP), and ncpmon.exe (both Sophos and NCP). The vulnerability exists because: (1) the VPN client requests update metadata over an insecure HTTP connection; and (2) the client software does not check if the software update is signed before running it. • https://www.ncp-e.com/en/resources/download-vpn-client/#c8680 https://www.ncp-e.com/fileadmin/pdf/service_support/release_notes/NCP_Secure_Clients/NCP_Secure_Entry_Client/NCP_RN_Win_Secure_Entry_Client_11_14_r42039_en.pdf • CWE-345: Insufficient Verification of Data Authenticity •
CVSS: 6.9EPSS: 0%CPEs: 3EXPL: 0CVE-2010-5203
https://notcve.org/view.php?id=CVE-2010-5203
Multiple untrusted search path vulnerabilities in NCP Secure Enterprise Client before 9.21 Build 68, Secure Entry Client before 9.23 Build 18, and Secure Client - Juniper Edition before 9.23 Build 18 allow local users to gain privileges via a Trojan horse (1) dvccsabase002.dll, (2) conman.dll, (3) kmpapi32.dll, or (4) ncpmon2.dll file in the current working directory, as demonstrated by a directory that contains a .pcf or .spd file. NOTE: some of these details are obtained from third party information. Múltiples vulnerabilidades de ruta de búsqueda no confiable en NCP Secure Enterprise Client anterior a 9.21 Build 68, Entry Client anterior a 9.23 Build 18, y Secure Client - Juniper Edition anterior a 9.23 Build 18 permite a usuarios locales obtener privilegios a través de un caballo de troya (1) dvccsabase002.dll, (2) conman.dll, (3) kmpapi32.dll, o (4) Archivo ncpmon2.dll en el directorio de trabajo actual, como lo demuestra un directorio que contiene un pcf. o. spd. NOTA: algunos de estos detalles han sido obtenidos a partir de información de terceros. • http://secunia.com/advisories/41388 http://www.ncp-e.com/fileadmin/pdf/service_support/NCP_Client_Vulnerability_Statement_EN.pdf •