# CVE-2024-29216: Missing authorization in cg6kwin2k.sys

> A local user can exploit an exposed IOCTL in the Sangoma driver to modify hardware firmware without administrator privileges.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2024
- **Updated:** 7 Nov 2024
- **Also known as:** GHSA-g2m6-m2m8-q4qh

## What is CVE-2024-29216?

CVE-2024-29216 is a medium-severity missing authorization vulnerability in cg6kwin2k.sys, published on 25 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Exposed IOCTL with insufficient access control issue exists in cg6kwin2k.sys prior to 2.1.7.0. By sending a specific IOCTL request, a user without the administrator privilege may perform I/O to arbitrary hardware port or physical address, resulting in erasing or altering the firmware.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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


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

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

## Is CVE-2024-29216 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29216 is a medium-severity missing authorization vulnerability in cg6kwin2k.sys, published on 25 Mar 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-29216 in the wild and no public exploit code.

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

## Sources

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

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