Skip to content

Instantly share code, notes, and snippets.

Created February 26, 2018 20:32
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
Star You must be signed in to star a gist
Embed
What would you like to do?
diff --git a/advisories/VS-2018-004.md b/advisories/VS-2018-004.md
index 642108a..ae4012d 100644
--- a/advisories/VS-2018-004.md
+++ b/advisories/VS-2018-004.md
@@ -15,7 +15,7 @@ PrivateVPN for MacOS < 2.0.31
PrivateVPN for MacOS suffers from a root privilege escalation vulnerability. The software installs a privileged helper tool that runs as the root user. This privileged helper tool is installed as a LaunchDaemon and implements an XPC service. The XPC service is responsible for handling new VPN connection operations via the main PrivateVPN application. The privileged helper tool creates new VPN connections by executing the **openvpn** binary located in the `/Applications/PrivateVPN.app/Contents/Resources` directory. The **openvpn** binary can be overwritten by the default user, which allows an attacker that has already installed malicious software as the default user to replace the binary. When a new VPN connection is established, the privileged helper tool will launch this malicious binary, thus allowing an attacker to execute code as the root user.
#### Vendor Response
-PrivateVPN stated the vulnerability is an acceptable part of their software.
+PrivateVPN confirmed update.
#### Disclosure Timeline
@@ -23,7 +23,7 @@ PrivateVPN stated the vulnerability is an acceptable part of their software.
* **02-20-2018** - Vendor contacted via Facebook
* **02-20-2018** - Vendor contacted via email
* **02-20-2018** - Vendor response and disclosure
-* **02-21-2018** - Vendor response: "Without helper, we cannot run openvpn. This is what all vpn apps are doing."
+* **02-21-2018** - Vendor response
* **02-21-2018** - Vendor notified of advisory release
#### Credit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment