Security readout for executives and security teams
Plain-English summary
ProtonVPN 1.3.3 for Windows can let a local malicious application gain SYSTEM-level control. The issue sits in the ProtonVPN Service, which exposes methods over a named pipe. Business impact is endpoint takeover risk where this specific client version is installed.
Executive priority
Treat as high priority if ProtonVPN 1.3.3 exists in the fleet. It is a local privilege escalation to SYSTEM, but evidence provided does not support internet-wide exposure or active exploitation.
Technical view
The ProtonVPN Service exposes a NetNamedPipe endpoint to arbitrary installed applications. The Connect method accepts attacker-controlled input that can influence the OpenVPN command line, including a dynamic library plugin loaded during new VPN connections. That plugin executes as SYSTEM.
Likely exposure
Exposure appears limited to Windows endpoints running ProtonVPN 1.3.3. The source bundle does not identify other affected versions, CPEs, or platforms.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires local application execution on an affected Windows host, then abuse of the service interface to reach SYSTEM privileges.
Researcher notes
Key evidence comes from the CVE record and VerSprite advisory reference. Missing data includes CVSS, CWE mapping, fixed version, and vendor remediation details. Do not broaden affected versions beyond ProtonVPN 1.3.3 for Windows without vendor evidence.
Mitigation direction
- Inventory Windows endpoints for ProtonVPN 1.3.3.
- Check ProtonVPN vendor guidance for patched or supported client versions.
- Remove or isolate affected clients until remediation is confirmed.
- Restrict untrusted application execution on affected endpoints.
- Monitor for unexpected SYSTEM-level VPN or OpenVPN child activity.
Validation and detection
- Confirm whether ProtonVPN 1.3.3 is installed on Windows endpoints.
- Verify whether the ProtonVPN Service is present and running.
- Review endpoint telemetry for unusual ProtonVPN or OpenVPN plugin loading.
- Check change records for remediation against vendor guidance.
- Prioritize validation on shared, developer, and high-privilege workstations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Privilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-10169 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/VerSprite/research/blob/master/advisories/VS-2018-017.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.