LiveActive security incident?Get immediate response
CVE Record

CVE-2018-11479: The VPN component in Windscribe 1.81 uses the OpenVPN client for connections.

The VPN component in Windscribe 1.81 uses the OpenVPN client for connections. Also, it creates a WindScribeService.exe system process that establishes a \\.\pipe\WindscribeService named pipe endpoint that allows the Windscribe VPN process to connect and execute an OpenVPN process or other processes (like taskkill, etc.). There is no validation of the program name before constructing the lpCommandLine argument for a CreateProcess call. An attacker can run any malicious process with SYSTEM privileges through this named pipe.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Windscribe VPN 1.81 created a privileged Windows service interface that could let an attacker start another program as SYSTEM. That means a compromised low-privilege endpoint user or process could potentially gain full local control of the machine. Exposure is most relevant to Windows endpoints running Windscribe VPN 1.81. The supplied CVE data does not identify other affected versions, platforms, CPEs, or deployment prerequisites beyond the Windscribe VPN service behavior. Treat this as high priority for affected endpoints because successful abuse could convert limited local access into SYSTEM-level control. Urgency depends on whether Windscribe 1.81 is present in the environment. Mitigation focus: Identify and remove or isolate Windscribe VPN 1.81 installations.; Check Windscribe vendor guidance for fixed versions or replacement builds.; Restrict local administrative access on affected Windows endpoints..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2018-11479 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.