# CVE-2022-24986: Race condition in n/a

> An attacker can intercept temporary files in KCron to execute unauthorized commands due to predictable filenames and race conditions.

- **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:** 26 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** DEBIAN-CVE-2022-24986, GHSA-5xwv-qfcf-c76h, UBUNTU-CVE-2022-24986, openSUSE-SU-2024:11881-1

## What is CVE-2022-24986?

CVE-2022-24986 is a high-severity vulnerability in n/a, published on 26 Feb 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

KDE KCron through 21.12.2 uses a temporary file in /tmp when saving, but reuses the filename during an editing session. Thus, someone watching it be created the first time could potentially intercept the file the following time, enabling that person to run unauthorized commands.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

It affects 1 product.


Products: Kde Kcron.

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

Apply the vendor's patch.

## Is CVE-2022-24986 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24986 is a high-severity vulnerability in n/a, published on 26 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-24986 in the wild and no public exploit code.

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

## Sources

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

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