# CVE-2022-21946: suddoers configuration for cscreen not restrictive enough

> Local users can escalate privileges to tty and dialout groups and manipulate running cscreen sessions due to restrictive sudoers configuration.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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 Mar 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wj8w-cmvq-mfv8

## What is CVE-2022-21946?

CVE-2022-21946 is a medium-severity 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 Incorrect Permission Assignment for Critical Resource vulnerability in the sudoers configuration in cscreen of openSUSE Factory allows any local users to gain the privileges of the tty and dialout groups and access and manipulate any running cscreen seesion. This issue affects: openSUSE Factory cscreen version 1.2-1.3 and prior versions.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Opensuse Cscreen.

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

Apply the vendor's patch.

## Is CVE-2022-21946 being exploited?

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

## Other vulnerabilities in openSUSE Factory

- [CVE-2022-21945](https://insights.sbomify.com/CVE-2022-21945/): cscreen: usage of fixed path /tmp/cscreen.debug (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21946 is a medium-severity 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-21946 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-21946/ (Markdown: https://insights.sbomify.com/CVE-2022-21946/index.md)
```

## Sources

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

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