Strix
26.1K

CVE-2018-11479

UnknownEPSS 9.90%

Last modified

CVE-2018-11479 is a vulnerability of currently unknown severity. 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.). EPSS estimates a 9.90% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
9.90%

95.0th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
WindscribeWindscribe1.81

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2018-11479?
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.
How severe is CVE-2018-11479?
Severity scoring for CVE-2018-11479 is pending analysis. The EPSS model estimates a 9.90% probability of exploitation in the next 30 days.
How do I fix CVE-2018-11479?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2018

View all 2018CVEs →

Are you affected by CVE-2018-11479?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST