Security readout for executives and security teams
Plain-English summary
PureVPN 6.0.1 for Windows can let a logged-in user gain SYSTEM-level control when the OpenVPN mode is used. The issue comes from a VPN configuration file that ordinary users can modify. That file can influence code loaded by the VPN service during connection attempts.
Executive priority
Treat this as high priority where PureVPN 6.0.1 exists on business Windows endpoints. It converts ordinary local access into SYSTEM control, but evidence provided does not show internet-scale or active exploitation.
Technical view
The sevpnclient service runs openvpn.exe using %PROGRAMDATA%\purevpn\config\config.ovpn. The source says this file grants Write permission to Everyone. An authenticated attacker can alter it to reference a dynamic library plugin that executes under the SYSTEM account during a new VPN connection attempt.
Likely exposure
Exposure appears limited to Windows systems running PureVPN 6.0.1 configured to use the OpenVPN protocol, especially shared workstations or systems where non-administrative users can log in locally.
Exploitation context
The bundle does not show KEV listing or active exploitation evidence. Exploitation requires authenticated local access and a later VPN connection attempt, but successful abuse can elevate privileges to SYSTEM.
Researcher notes
The public record provides a clear local privilege-escalation mechanism but no CVSS, CWE, fixed version, or vendor mitigation details in the supplied bundle. Scope findings carefully to PureVPN 6.0.1 for Windows with OpenVPN configuration.
Mitigation direction
- Check PureVPN or vendor guidance for fixed releases or supported mitigations.
- Remove or disable PureVPN 6.0.1 for Windows where it is not required.
- Prioritize upgrade or replacement on shared or multi-user Windows endpoints.
- Limit local interactive access to affected endpoints until remediated.
- Monitor for unexpected changes to PureVPN OpenVPN configuration files.
Validation and detection
- Inventory Windows endpoints for PureVPN 6.0.1 installations.
- Confirm whether PureVPN is configured to use the OpenVPN protocol.
- Review permissions on %PROGRAMDATA%\purevpn\config\config.ovpn.
- Check whether non-administrative users can modify the configuration file.
- Review endpoint telemetry for unusual VPN configuration changes.
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-10204 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-021.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.