Bernd Leitner

A local privilege escalation issue has been identified due to over-permissive configuration settings and a SUID binary, allowing an attacker to execute arbitrary binaries as root.

A local privilege escalation issue has been identified, allowing an attacker to communicate with an unprotected XPC service. This enables the execution of arbitrary OS commands as root or the loading of a potentially malicious kernel extension. The issue arises because `com.smr.liquidvpn.OVPNHelper` uses the system function to execute the `openvpncmd` parameter as a shell command.

A local privilege escalation issue has been identified, allowing an attacker to communicate with an unprotected XPC service. This enables the execution of arbitrary OS commands as root or the loading of a potentially malicious kernel extension. The issue arises because `com.smr.liquidvpn.OVPNHelper` uses the system function to execute the `command line` parameter as a shell command.

The issue allows an attacker to communicate with an unprotected XPC service, enabling the execution of arbitrary OS commands as root or the loading of a potentially malicious kernel extension. This is possible because `com.smr.liquidvpn.OVPNHelper` uses the system function to execute the `tun path` or `tap path` pathname within a shell command.

The issue allows an attacker to communicate with an unprotected XPC service, enabling the execution of arbitrary OS commands as root or the loading of a potentially malicious kernel extension. This is possible because `com.smr.liquidvpn.OVPNHelper` uses the value of the `tun path` or `tap path` pathname in a `kextload()` call.