dbcve.org
OpenvpnApplication

CVE-2024-24974

HIGH · 7.5 CVSS v3.1 Published 2024-07-08
Fix available
A fix is available. Upgrade to 2.5.10 / 2.6.10 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
The interactive service in OpenVPN 2.6.9 and earlier allows the OpenVPN service pipe to be accessed remotely, which allows a remote attacker to interact with the privileged OpenVPN interactive service.

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 · moderate confidence

The OpenVPN interactive service in versions 2.6.9 and earlier contains a vulnerability where the service pipe can be accessed remotely, allowing an unauthenticated remote attacker to interact with the privileged OpenVPN interactive service. This enables potential manipulation of VPN operations without proper authorization.

MitigationRestrict network access to the OpenVPN service through firewall rules and network segmentation until a patched version is available. Review and minimize the attack surface of the interactive service.

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
OpenvpnApplication
Affected:< 2.5.10>= 2.6.0, < 2.6.10

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Identify OpenVPN version
    Run 'openvpn --version' or check the installed version through the system's package manager (e.g., 'dpkg -l openvpn', 'rpm -qi openvpn', or via Windows Programs and Features)
    Affected if The version displayed is below 2.5.10, or is 2.6.0 through 2.6.9 (e.g., 2.6.0, 2.6.5, 2.6.9)
  2. Confirm OpenVPN Interactive Service presence
    On Windows, check for 'OpenVPN Interactive Service' in Services (services.msc) or via 'sc query' command; on Linux, check for openvpn-interactive-service package installation
    Affected if The OpenVPN Interactive Service is installed and running on the system
  3. Verify service pipe exposure
    Check firewall rules and network configuration for any allowed inbound access to the service port or named pipe endpoint. On Windows, inspect the service's ACLs or look for any listening endpoints related to the interactive service.
    Affected if The service is network-accessible (e.g., listening on a port or accessible via named pipe from remote systems) and no restrictive firewall rules are in place to block unauthorized remote access to it
  4. Review service configuration
    Examine the OpenVPN service configuration files and registry keys (HKLM\SYSTEM\CurrentControlSet\Services\OpenVPNInteractiveService on Windows) for any settings that enable remote pipe access or disable authentication
    Affected if Configuration allows unauthenticated remote interaction or explicitly enables remote pipe access

The environment is affected if the installed OpenVPN version is below 2.5.10 or between 2.6.0 and 2.6.9 inclusive AND the OpenVPN Interactive Service is running and accessible remotely.

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.

dbcve · scoped
Upgrade available Upgrade to 2.5.10 / 2.6.10 or later
Fixed in 2.5.102.6.10
Interim mitigation

Restrict network access to the OpenVPN service through firewall rules and network segmentation until a patched version is available. Review and minimize the attack surface of the interactive service.

Recommended fix High confidence

OpenVPN 2.5.10 or 2.6.10 (whichever branch matches your current installation)

  1. 1. Check the current OpenVPN version using 'openvpn --version' or 'openvpn -v'
  2. 2. For OpenVPN 2.5.x users: Upgrade to version 2.5.10 or later
  3. 3. For OpenVPN 2.6.x users: Upgrade to version 2.6.10 or later
  4. 4. After upgrading, restart the OpenVPN service using 'systemctl restart openvpn' or the appropriate service command for your system
  5. 5. Verify the new version is running with 'openvpn --version'
Caveat Review OpenVPN release notes for any configuration or feature changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openvpn Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-24974 — 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-2024-24974 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