# CVE-2022-28368: Remote code injection in dompdf/dompdf

> Remote attackers can execute arbitrary code by uploading a PHP file referenced in a CSS font-face URL within an HTML input.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 3 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-x752-qjv4-c4hc

## What is CVE-2022-28368?

CVE-2022-28368 is a critical code injection vulnerability in n/a, published on 3 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dompdf 1.2.1 allows remote code execution via a .php file in the src:url field of an @font-face Cascading Style Sheets (CSS) statement (within an HTML input file).

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

2 open source packages ship an affected version, including dompdf/dompdf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dompdf/dompdf` | Packagist | All versions | 1.2.1 |
| `dompdf/dompdf` | Packagist | All versions | 1.2.1 |

Products: Dompdf Project Dompdf.

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

Upgrade dompdf/dompdf to 1.2.1 or later.

## Is CVE-2022-28368 being exploited?

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

Public exploit code:

- Dompdf RCE PoC Exploit - CVE-2022-28368 (github_poc): https://github.com/rvzsec/CVE-2022-28368
- Dompdf RCE via Malicious Font Caching (CVE-2022-28368) (metasploit)
- Dompdf 1.2.1 - Remote Code Execution (RCE) (exploitdb)
- This repository contains a python script that will handle the majority of the dompdf cached font exploit (CVE-2022-28368), all you need to do is create the request (github_poc): https://github.com/That-Guy-Steve/CVE-2022-28368-handler
- An exploit script for CVE-2022-28368 designed to make exploitation less annoying, made for a HTB machine (github_poc): https://github.com/Henryisnotavailable/Dompdf-Exploit-RCE

## Other vulnerabilities in n/a

- [CVE-2023-24813](https://insights.sbomify.com/CVE-2023-24813/): URI validation failure on SVG parsing. Bypass of CVE-2023-23924 (critical 10.0)
- [CVE-2023-23924](https://insights.sbomify.com/CVE-2023-23924/): URI validation failure on SVG parsing in Dompdf (critical 10.0)
- [CVE-2021-3838](https://insights.sbomify.com/CVE-2021-3838/): PHAR Deserialization in dompdf/dompdf (critical 9.8)
- [CVE-2021-3902](https://insights.sbomify.com/CVE-2021-3902/): Improper Restriction of XML External Entity Reference in dompdf/dompdf (critical 9.8)
- [CVE-2014-5013](https://insights.sbomify.com/CVE-2014-5013/): DOMPDF Remote Code Execution (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28368 is a critical code injection vulnerability in n/a, published on 3 Apr 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-28368 exists.

Affected packages and fixed versions:
- dompdf/dompdf (Packagist): affected all versions; fixed in 1.2.1
- dompdf/dompdf (Packagist): affected all versions; fixed in 1.2.1

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

## Sources

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

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