Skip to content
Fencer Intel
high 7.8

CVE-2018-11479 json

The VPN component in Windscribe 1.81 uses the OpenVPN client for connections.

published 8y ago modified 4mo ago also EUVD-2018-3510

cvss
7.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.6%
EPSS 9.6% chance of exploitation in 30 days, percentile 95%
public exploits
2
Metasploit and Exploit-DB

Summary

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.

Is CVE-2018-11479 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/local/windscribe_windscribeservice_priv_esc)
  2. Published

Exploit prediction

9.58% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.0 7.8 CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.