# CVE-2022-31250: keylime %post scriplet allows for privilege escalation from keylime user to root

> Local attackers can escalate privileges from the keylime user to root via a symlink following vulnerability in the post-installation script.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 20 Jul 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-frfj-3v3x-pvwx, openSUSE-SU-2024:12153-1

## What is CVE-2022-31250?

CVE-2022-31250 is a high-severity vulnerability in openSUSE Tumbleweed, published on 20 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A UNIX Symbolic Link (Symlink) Following vulnerability in keylime of openSUSE Tumbleweed allows local attackers to escalate from the keylime user to root. This issue affects: openSUSE Tumbleweed keylime versions prior to 6.4.2-1.1.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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

It affects 1 product.


Products: Opensuse Tumbleweed.

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

Upgrade to a fixed version.

## Is CVE-2022-31250 being exploited?

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

## Other vulnerabilities in openSUSE Tumbleweed

- [CVE-2023-32183](https://insights.sbomify.com/CVE-2023-32183/): Privilege escalation in Tumbleweed (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-31250 is a high-severity vulnerability in openSUSE Tumbleweed, published on 20 Jul 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-31250 in the wild and no public exploit code.

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

## Sources

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

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