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

> An attacker can cause a denial of service by providing a specially crafted PCF font file to the pcf2bdf utility, triggering a segmentation fault.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 17 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-23319, GHSA-p4gv-mjgc-3g68, UBUNTU-CVE-2022-23319

## What is CVE-2022-23319?

CVE-2022-23319 is a medium-severity denial of service vulnerability in n/a, published on 17 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A segmentation fault during PCF file parsing in pcf2bdf versions >=1.05 allows an attacker to trigger a program crash via a specially crafted PCF font file. This crash affects the availability of the software and dependent downstream components.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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

It affects 1 product.


Products: Pcf2bdf Project Pcf2bdf.

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

Upgrade to a fixed version.

## Is CVE-2022-23319 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-23318](https://insights.sbomify.com/CVE-2022-23318/): Memory corruption in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23319 is a medium-severity denial of service vulnerability in n/a, published on 17 Feb 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-23319 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-23319/ (Markdown: https://insights.sbomify.com/CVE-2022-23319/index.md)
```

## Sources

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

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