# CVE-2022-33749: Denial of service in Xapi

> An unauthenticated network attacker can exhaust XAPI file descriptors, causing a denial of service for trusted clients and administrative tasks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALPINE-CVE-2022-33749, GHSA-v88g-q782-jgp2

## What is CVE-2022-33749?

CVE-2022-33749 is a medium-severity denial of service vulnerability in Xapi, published on 11 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XAPI open file limit DoS It is possible for an unauthenticated client on the network to cause XAPI to hit its file-descriptor limit. This causes XAPI to be unable to accept new requests for other (trusted) clients, and blocks XAPI from carrying out any tasks that require the opening of file descriptors.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Xen Xapi.

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

Apply the vendor's patch.

## Is CVE-2022-33749 being exploited?

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

## Other vulnerabilities in Xapi

- [CVE-2020-29487](https://insights.sbomify.com/CVE-2020-29487/): Denial of service in n/a (high 7.5)
- [CVE-2024-31144](https://insights.sbomify.com/CVE-2024-31144/): Xapi: Metadata injection attack against backup/restore functionality (low 3.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-33749 is a medium-severity denial of service vulnerability in Xapi, published on 11 Oct 2022. 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-2022-33749 in the wild and no public exploit code.

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

## Sources

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

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