# CVE-2022-25255: Path traversal in n/a

> An attacker can execute arbitrary binaries from the current working directory via QProcess, leading to code execution.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** ALSA-2022:7482, ALSA-2022:8022, AZL-50050, DEBIAN-CVE-2022-25255, GHSA-fw78-qp2x-5gc7, OESA-2022-1787, OESA-2022-1803, RHSA-2022:7482, RHSA-2022:8022, RLSA-2022:7482, RLSA-2022:8022, UBUNTU-CVE-2022-25255, openSUSE-SU-2024:11879-1, openSUSE-SU-2024:11886-1, openSUSE-SU-2024:11974-1

## What is CVE-2022-25255?

CVE-2022-25255 is a high-severity path traversal vulnerability in Qt Qt, published on 16 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In Qt 5.9.x through 5.15.x before 5.15.9 and 6.x before 6.2.4 on Linux and UNIX, QProcess could execute a binary from the current working directory when not found in the PATH.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qt5-devel` | AlmaLinux:8 | All versions | 5.15.3-1.el8 |
| `qt5-rpm-macros` | AlmaLinux:8 | All versions | 5.15.3-1.el8 |
| `qt5-srpm-macros` | AlmaLinux:8 | All versions | 5.15.3-1.el8 |
| `qt5` | AlmaLinux:9 | All versions | 5.15.3-1.el9 |
| `qt5-devel` | AlmaLinux:9 | All versions | 5.15.3-1.el9 |
| `qt5-rpm-macros` | AlmaLinux:9 | All versions | 5.15.3-1.el9 |
| `qt5-srpm-macros` | AlmaLinux:9 | All versions | 5.15.3-1.el9 |
| `qt5` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.15.3-1.el8 |
| `qt5-rpm-macros` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.15.3-1.el8 |
| `qt5-srpm-macros` | Red Hat:enterprise_linux:8::appstream | All versions | 0:5.15.3-1.el8 |
| `qt5-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:5.15.3-1.el8 |
| `qt5` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.15.3-1.el9 |
| `qt5-rpm-macros` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.15.3-1.el9 |
| `qt5-srpm-macros` | Red Hat:enterprise_linux:9::appstream | All versions | 0:5.15.3-1.el9 |
| `qt5-devel` | Red Hat:enterprise_linux:9::crb | All versions | 0:5.15.3-1.el9 |
| `qt5` | Rocky Linux:8 | All versions | 0:5.15.3-1.el8 |
| `qt5` | Rocky Linux:9 | All versions | 0:5.15.3-1.el9 |
| `libqt5-qtbase` | openSUSE:Tumbleweed | All versions | 5.15.2+kde294-4.1 |
| `qt6-base` | openSUSE:Tumbleweed | All versions | 6.2.3-2.1 |
| `qutebrowser` | openSUSE:Tumbleweed | All versions | 2.5.0-1.1 |

Products: Qt Qt.

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

Upgrade to a fixed version.

## Is CVE-2022-25255 being exploited?

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

## Other vulnerabilities in Qt Qt

- [CVE-2020-12267](https://insights.sbomify.com/CVE-2020-12267/): Use after free in n/a (critical 9.8)
- [CVE-2017-10904](https://insights.sbomify.com/CVE-2017-10904/): Command injection in Qt for Android (critical 9.8)
- [CVE-2011-3194](https://insights.sbomify.com/CVE-2011-3194/): Memory corruption in n/a (critical 9.3)
- [CVE-2022-40983](https://insights.sbomify.com/CVE-2022-40983/): Integer overflow in Qt (high 8.8)
- [CVE-2022-43591](https://insights.sbomify.com/CVE-2022-43591/): Memory corruption in Qt (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-25255 is a high-severity path traversal vulnerability in Qt Qt, published on 16 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-25255 in the wild and no public exploit code.

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

## Sources

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

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