dbcve.org
Classic Buffer OverflowWeakness · CWE-120

CVE-2024-30165

HIGH · 7.1 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 →
73/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 before 3.9.1 on macOS has a buffer overflow that could potentially allow a local actor to execute arbitrary commands with elevated permissions, a different vulnerability than CVE-2024-30164.

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

Amazon AWS Client VPN for macOS versions prior to 3.9.1 contains a buffer overflow vulnerability in the client software that can be exploited by a local attacker to achieve arbitrary command execution with elevated privileges. The flaw appears to stem from insufficient bounds checking within the VPN client's processing of certain data, allowing a malicious local user to overflow a buffer and redirect execution flow.

MitigationUpdate Amazon AWS Client VPN to version 3.9.1 or later on all affected macOS systems to remediate this vulnerability. In enterprise environments, test the update for compatibility with existing VPN configurations before broad deployment.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Verify AWS Client VPN is installed
    Check if the AWS Client VPN application exists in /Applications folder by running: ls -la /Applications/ | grep -i 'AWS.*VPN' or by searching in Finder
    Affected if The application is present in the system
  2. Determine installed version number
    Run in Terminal: defaults read /Applications/AWS\ Client\ VPN.app/Contents/Info.plist CFBundleShortVersionString or use: mdls -name kCFBundleShortVersionString /Applications/AWS\ Client\ VPN.app
    Affected if A version number is returned from the command
  3. Compare version against affected range
    Compare the obtained version number to 3.9.1 - versions prior to 3.9.1 are affected (e.g., 3.9.0, 3.8.0, 3.7.0, etc.)
    Affected if Installed version is less than 3.9.1 (e.g., 3.8.0, 3.7.2, etc.)
  4. Confirm macOS platform
    Verify the system is running macOS: uname -a shows Darwin, or System Preferences > About shows macOS
    Affected if The target system is running macOS and has the vulnerable client installed

A system is affected if AWS Client VPN for macOS is installed and the version number is below 3.9.1, making it vulnerable to local privilege escalation via buffer overflow.

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 Amazon AWS Client VPN to version 3.9.1 or later on all affected macOS systems to remediate this vulnerability. In enterprise environments, test the update for compatibility with existing VPN configurations before broad deployment.

Recommended fix High confidence

AWS Client VPN version 3.9.1 or later for macOS

  1. 1. Open the AWS Client VPN application on your macOS system
  2. 2. Navigate to the application menu and select 'Check for Updates' or 'About AWS Client VPN'
  3. 3. If an update is available, download and install version 3.9.1 or later
  4. 4. Alternatively, download the latest version of AWS Client VPN for macOS from the official AWS website
  5. 5. Restart the VPN client after installation to ensure the patched version is running
  6. 6. Verify the installed version by checking 'About AWS Client VPN' to confirm version 3.9.1 or higher is running

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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