# CVE-2022-21945: cscreen: usage of fixed path /tmp/cscreen.debug

> Local attackers can cause denial of service in cscreen and potentially the system by exploiting an insecure temporary file path.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-xxwq-xf8c-v665

## What is CVE-2022-21945?

CVE-2022-21945 is a medium-severity path traversal vulnerability in openSUSE Factory, published on 16 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A Insecure Temporary File vulnerability in cscreen of openSUSE Factory allows local attackers to cause DoS for cscreen and a system DoS for non-default systems. This issue affects: openSUSE Factory cscreen version 1.2-1.3 and prior versions.

Weakness: CWE-377 (DEPRECATED: Insecure Temporary File)

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

It affects 1 product.


Products: Opensuse Cscreen.

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

Apply the vendor's patch.

## Is CVE-2022-21945 being exploited?

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

## Other vulnerabilities in openSUSE Factory

- [CVE-2022-21946](https://insights.sbomify.com/CVE-2022-21946/): suddoers configuration for cscreen not restrictive enough (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21945 is a medium-severity path traversal vulnerability in openSUSE Factory, published on 16 Mar 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-21945 in the wild and no public exploit code.

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

## Sources

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

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