dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2024-30164

MEDIUM · 6.7 CVSS v3.1 Published 2024-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
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
Amazon AWS Client VPN has a buffer overflow that could potentially allow a local actor to execute arbitrary commands with elevated permissions. This is resolved in 3.11.1 on Windows, 3.9.1 on macOS, and 3.12.1 on Linux. NOTE: although the macOS resolution is the same as for CVE-2024-30165, this vulnerability on macOS is not the same as CVE-2024-30165.

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

AWS Client VPN contains a buffer overflow vulnerability that could allow a local attacker to execute arbitrary commands with elevated privileges. The vulnerability exists across Windows, macOS, and Linux platforms and is caused by improper bounds checking in the VPN client software.

MitigationUpdate AWS Client VPN to version 3.11.1 or later on Windows, 3.9.1 or later on macOS, or 3.12.1 or later on Linux.

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

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

CVSS:3.1/AV:L/AC:L/PR:H/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. Verify AWS Client VPN is installed
    Search for AWS Client VPN on the system. On Windows, check Program Files or the Start menu. On macOS, check /Applications for AWS Client VPN.app. On Linux, check common binary paths like /usr/bin, /usr/local/bin, or /opt.
    Affected if AWS Client VPN software is present on the system
  2. Determine installed version number
    On Windows, right-click the AWS Client VPN executable and select Properties > Details to view the File Version. On macOS, right-click AWS Client VPN.app in Applications and select Get Info to see the Version. On Linux, run 'awsclientvpn --version' or query the installed package via the system package manager.
    Affected if A version number is obtained for comparison
  3. Compare against affected version thresholds
    Match your detected version to the threshold for your platform: Windows versions below 3.11.1 are affected; macOS versions below 3.9.1 are affected; Linux versions below 3.12.1 are affected.
    Affected if The installed version is below 3.11.1 on Windows, below 3.9.1 on macOS, or below 3.12.1 on Linux

The environment is affected if AWS Client VPN is installed and its version number is lower than the threshold for the detected platform (3.11.1 for Windows, 3.9.1 for macOS, 3.12.1 for Linux).

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update AWS Client VPN to version 3.11.1 or later on Windows, 3.9.1 or later on macOS, or 3.12.1 or later on Linux.

Recommended fix High confidence

Windows: 3.11.1 or later | macOS: 3.9.1 or later | Linux: 3.12.1 or later

  1. Identify the operating system where AWS Client VPN is installed (Windows, macOS, or Linux)
  2. Check the currently installed version of AWS Client VPN
  3. For Windows: Download and install version 3.11.1 or later from the official AWS Client VPN download page
  4. For macOS: Download and install version 3.9.1 or later from the official AWS Client VPN download page
  5. For Linux: Download and install version 3.12.1 or later from the official AWS Client VPN download page
  6. Verify the installation was successful by confirming the installed version matches or exceeds the appropriate fixed version for your platform

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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