# CVE-2024-1305: Integer overflow in OpenVPN-GUI

> An attacker can trigger a kernel buffer overflow via crafted write operations, leading to arbitrary code execution and privilege escalation on Windows systems using the vulnerable driver.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jul 2024
- **Updated:** 23 Aug 2024
- **Also known as:** GHSA-fv4p-hrvc-c34g

## What is CVE-2024-1305?

CVE-2024-1305 is a critical vulnerability in OpenVPN-GUI, published on 8 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tap-windows6 driver version 9.26 and earlier does not properly 
check the size data of incomming write operations which an attacker can 
use to overflow memory buffers, resulting in a bug check and potentially
 arbitrary code execution in kernel space

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Openvpn Tap-Windows6.

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

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

## Is CVE-2024-1305 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-1305 is a critical vulnerability in OpenVPN-GUI, published on 8 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1305 in the wild and no public exploit code.

Affected product: OpenVPN-GUI. 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-1305/ (Markdown: https://insights.sbomify.com/CVE-2024-1305/index.md)
```

## Sources

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

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