# CVE-2022-46770: Denial of service in n/a

> Guest OS users can cause denial of service in QubesOS Mirage firewall via crafted multicast UDP packets, leading to CPU exhaustion and loss of forwarding.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-6vx5-8rxp-jw26, OSEC-2022-01

## What is CVE-2022-46770?

CVE-2022-46770 is a high-severity denial of service vulnerability in n/a, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qubes-mirage-firewall (aka Mirage firewall for QubesOS) 0.8.x through 0.8.3 allows guest OS users to cause a denial of service (CPU consumption and loss of forwarding) via a crafted multicast UDP packet (IP address range of 224.0.0.0 through 239.255.255.255).

Weakness: CWE-835 (Loop with Unreachable Exit Condition)

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

It affects 1 product.


Products: Linuxfoundation Mirage Firewall.

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

Upgrade to a fixed version.

## Is CVE-2022-46770 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46770 exists.

Public exploit code:

- Mirage firewall for QubesOS 0.8.0-0.8.3 Denial of Service (DoS) Exploit (metasploit)
- qubes-mirage-firewall  v0.8.3 - Denial Of Service (DoS) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46770 is a high-severity denial of service vulnerability in n/a, published on 7 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46770 exists.

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-2022-46770/ (Markdown: https://insights.sbomify.com/CVE-2022-46770/index.md)
```

## Sources

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

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