# CVE-2024-30164: Memory corruption in n/a

> A local attacker can exploit a buffer overflow in AWS Client VPN to execute arbitrary commands with elevated permissions.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-30164?

CVE-2024-30164 is a medium-severity memory corruption vulnerability in n/a, published on 28 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-30164?


## How do I fix CVE-2024-30164?

No fix has been published for CVE-2024-30164 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-30164 being exploited?

There is no known exploitation of CVE-2024-30164 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-30164 and fix it if it is affected.

What it is: CVE-2024-30164 is a medium-severity memory corruption vulnerability in n/a, published on 28 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-30164 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-30164/ (Markdown: https://insights.sbomify.com/CVE-2024-30164/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-30164
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-30164
- OSV: https://osv.dev/vulnerability/CVE-2024-30164

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-30164/
Summaries are generated and may contain mistakes; the official description above is the record.