dbcve.org
VyprvpnApplication · Goldenfrog

CVE-2018-10645

HIGH · 7.8 CVSS v3.0 Published 2018-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Golden Frog VyprVPN 2.12.1.8015 for Windows suffers from a SYSTEM privilege escalation vulnerability through the "VyprVPN" service. This service establishes a NetNamedPipe endpoint that allows applications to connect and call publicly exposed methods. The "SetProperty" method allows an attacker to configure the "AdditionalOpenVpnParameters" property and control the OpenVPN command line. Using the OpenVPN "plugin" parameter, an attacker may specify a dynamic library plugin that should run for every new VPN connection attempt. This plugin will execute code in the context of the SYSTEM user. This attack may be conducted using "VyprVPN Free" account credentials and the VyprVPN Desktop Client.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The VyprVPN Windows service exposes a NetNamedPipe endpoint with a publicly accessible SetProperty method. Unprivileged users can call this method to configure the AdditionalOpenVpnParameters property, specifically using OpenVPN's plugin parameter to specify a DLL that will execute with SYSTEM privileges on every VPN connection attempt.

MitigationImplement proper authentication and authorization checks on the NetNamedPipe endpoint to ensure only privileged users can call SetProperty; alternatively, run the VyprVPN service with reduced privileges until a vendor patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VyprvpnApplication
Affected:= 2.12.1.8015

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if VyprVPN service is installed
    Open Services console (services.msc) or run 'sc query VyprVPN' to see if the service exists
    Affected if The VyprVPN service named 'VyprVPN' or similar is present on the system
  2. Identify installed VyprVPN version
    Check the file version of the main executable (typically in Program Files\Golden Frog\VyprVPN or similar path) - right-click the .exe file, select Properties, and view the Details tab for version information
    Affected if The version equals exactly 2.12.1.8015
  3. Verify VyprVPN service is running
    Run 'sc query VyprVPN' or check the Services console to confirm the service status is Running
    Affected if The service is currently running and exposes the vulnerable NetNamedPipe endpoint
  4. Check service executable path
    Run 'sc qc VyprVPN' to retrieve the service binary path, then verify the executable exists at that location
    Affected if The service points to a VyprVPN executable at the expected installation path
  5. Confirm service runs with elevated privileges
    Run 'sc queryex VyprVPN' to check the process ID, then use Task Manager or 'wmic process where processid=XXX get name,username' to verify it runs under SYSTEM or a high-privilege account
    Affected if The service runs under a high-privilege account (SYSTEM, LocalSystem, or similar), which would allow the plugin DLL to execute with those privileges

You are affected if VyprVPN version 2.12.1.8015 is installed and the service is currently running, exposing the unauthenticated NetNamedPipe endpoint that allows unprivileged users to set OpenVPN plugin parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authentication and authorization checks on the NetNamedPipe endpoint to ensure only privileged users can call SetProperty; alternatively, run the VyprVPN service with reduced privileges until a vendor patch is available.

Fix this in Vyprvpn Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10645 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10645 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data