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

> Remote attackers can cause a permanent denial of service on Xerox VersaLink devices by sending a crafted TIFF file, requiring a field technician to resolve the boot loop.

- **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:** No
- **Published:** 26 Jan 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4749-xq6x-59v3

## What is CVE-2022-23968?

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

### Official description

Xerox VersaLink devices on specific versions of firmware before 2022-01-26 allow remote attackers to brick the device via a crafted TIFF file in an unauthenticated HTTP POST request. There is a permanent denial of service because image parsing causes a reboot, but image parsing is restarted as soon as the boot process finishes. However, this boot loop can be resolved by a field technician. The TIFF file must have an incomplete Image Directory. Affected firmware versions include xx.42.01 and xx.50.61. NOTE: the 2022-01-24 NeoSmart article included "believed to affect all previous and later versions as of the date of this posting" but a 2022-01-26 vendor statement reports "the latest versions of firmware are not vulnerable to this issue."

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

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

It affects 1 product.


Products: Xerox Versalink Firmware.

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

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

## Is CVE-2022-23968 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23968 is a high-severity denial of service vulnerability in n/a, published on 26 Jan 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-23968 in the wild and no public exploit code.

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

## Sources

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

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