Local security-control removal via uninstaller hook bypass
Published Mar 14, 2024 · Updated Aug 1, 2024
Improper hook-argument validation in Skyhigh Client Proxy 4.8.1 and earlier allows local users to uninstall the client without its password. The vendor identifies API hooking in the Windows uninstaller challenge-response path as the bypass locus but does not publish the flawed hook or validation logic. Low-privilege local access is required; successful exploitation removes the traffic-enforcement client and impairs its security controls without directly exposing stored data.
Summary
What happened
Improper hook-argument validation in Skyhigh Client Proxy 4.8.1 and earlier allows local users to uninstall the client without its password. The vendor identifies API hooking in the Windows uninstaller challenge-response path as the bypass locus but does not publish the flawed hook or validation logic. Low-privilege local access is required; successful exploitation removes the traffic-enforcement client and impairs its security controls without directly exposing stored data.
The record
- CVE
- CVE-2024-0312
- Published
- Mar 14, 2024
- Updated
- Aug 1, 2024
- Vendor
- Skyhigh Security
- Product
- Skyhigh Client Proxy
- Classifications
- CWE-622, CAPEC-554, T1685
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo