Authenticated privileged-service access via remotely exposed named pipe
Published Jul 8, 2024 · Updated Aug 10, 2024
Improper channel restriction in OpenVPN 2.6.9 and earlier allows remote authenticated users to access its privileged Windows service. The openvpnserv.exe service creates the \openvpn\service named pipe without rejecting remote clients, allowing remote requests to launch operations. Network access requires valid credentials for a member of the OpenVPN Administrators group; this CVE alone exposes service interaction, not code execution.
Summary
What happened
Improper channel restriction in OpenVPN 2.6.9 and earlier allows remote authenticated users to access its privileged Windows service. The openvpnserv.exe service creates the \openvpn\service named pipe without rejecting remote clients, allowing remote requests to launch operations. Network access requires valid credentials for a member of the OpenVPN Administrators group; this CVE alone exposes service interaction, not code execution.
The record
- CVE
- CVE-2024-24974
- Published
- Jul 8, 2024
- Updated
- Aug 10, 2024
- Vendor
- OpenVPN Inc.
- Product
- OpenVPN
- Classifications
- CWE-923, T1021.002
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 8, 2024CVE publishedPublication date reported by the CVE source.
- Aug 10, 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=0 <2.5.10
- Affected versionversion=2.6.0 <2.6.10
- Affected versionversion=2.6.9 and earlier
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
- Microsoft OVPNX remote named-pipe chain demonstrationproof of concept · demonstrated
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