# CVE-2022-4583: jLEMS JUtil.java unpackJar path traversal

> A path traversal vulnerability in jLEMS allows remote attackers to read or modify arbitrary files via the unpackJar function.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-vwgc-p6h9-jq52

## What is CVE-2022-4583?

CVE-2022-4583 is a medium-severity path traversal vulnerability in unspecified jLEMS, published on 17 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in jLEMS. It has been declared as critical. Affected by this vulnerability is the function unpackJar of the file src/main/java/org/lemsml/jlems/io/util/JUtil.java. The manipulation leads to path traversal. The attack can be launched remotely. The name of the patch is 8c224637d7d561076364a9e3c2c375daeaf463dc. It is recommended to apply a patch to fix this issue. The identifier VDB-216169 was assigned to this vulnerability.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Neuroml Jlems.

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

No fix has been published for CVE-2022-4583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-4583 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4583 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4583 is a medium-severity path traversal vulnerability in unspecified jLEMS, published on 17 Dec 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-4583 exists.

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

## Sources

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

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