# CVE-2022-24913: Java Merge-sort Insecure Temporary File vulnerability

> An attacker can read temporary file contents due to insecure file creation in the java-merge-sort library.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 12 Jan 2023
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-qxxc-7mq4-mf79

## What is CVE-2022-24913?

CVE-2022-24913 is a medium-severity vulnerability in com.fasterxml.util:java-merge-sort, published on 12 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Versions of the package com.fasterxml.util:java-merge-sort before 1.1.0 are vulnerable to Insecure Temporary File in the StdTempFileProvider() function in StdTempFileProvider.java, which uses the permissive File.createTempFile() function, exposing temporary file contents.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-377 (DEPRECATED: Insecure Temporary File)

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

2 open source packages ship an affected version, including com.fasterxml.util:java-merge-sort. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.fasterxml.util:java-merge-sort` | Maven | All versions | 1.1.0 |
| `com.fasterxml.util:java-merge-sort` | Maven | All versions | 1.1.0 |

Products: Java-Merge-Sort Project Java-Merge-Sort.

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

Upgrade com.fasterxml.util:java-merge-sort to 1.1.0 or later.

## Is CVE-2022-24913 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24913 is a medium-severity vulnerability in com.fasterxml.util:java-merge-sort, published on 12 Jan 2023. 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-24913 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.fasterxml.util:java-merge-sort (Maven): affected all versions; fixed in 1.1.0
- com.fasterxml.util:java-merge-sort (Maven): affected all versions; fixed in 1.1.0

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

## Sources

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

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