# CVE-2022-32966: Realtek RTL8111FP-CG - Missing Authorization

> An unauthenticated attacker on the adjacent network can disrupt service via the DASH remote management function due to missing authorization.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Nov 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-33mr-h3pf-4jg7

## What is CVE-2022-32966?

CVE-2022-32966 is a medium-severity missing authorization vulnerability in Realtek RTL8111FP-CG, published on 29 Nov 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

RTL8168FP-CG Dash remote management function has missing authorization. An unauthenticated attacker within the adjacent network can connect to DASH service port to disrupt service.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-32966?

It affects 1 product.


Products: Realtek Rtl8111fp-Cg Firmware.

## How do I fix CVE-2022-32966?

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

## Is CVE-2022-32966 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-32966 and fix it if it is affected.

What it is: CVE-2022-32966 is a medium-severity missing authorization vulnerability in Realtek RTL8111FP-CG, published on 29 Nov 2022. 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-2022-32966 in the wild and no public exploit code.

Affected product: Realtek RTL8111FP-CG. 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-2022-32966/ (Markdown: https://insights.sbomify.com/CVE-2022-32966/index.md)
```

## Sources

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

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