# CVE-2022-38731: Path traversal in n/a

> Attackers can read arbitrary files and coerce authentication via UNC paths in Qaelum DOSE due to improper input validation in the image loading parameter.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-qvw2-4h5w-2c5p

## What is CVE-2022-38731?

CVE-2022-38731 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Qaelum DOSE 18.08 through 21.1 before 21.2 allows Directory Traversal via the loadimages name parameter. It allows a user to specify an arbitrary location on the server's filesystem from which to load an image. (Only images are displayed to the attacker. All other files are loaded but not displayed.) The Content-Type response header reflects the actual content type of the file being requested. This allows an attacker to enumerate files on the local system. Additionally, remote resources can be requested via a UNC path, allowing an attacker to coerce authentication out from the server to the attackers machine.

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

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

It affects 1 product.


Products: Qaelum Dose.

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

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

## Is CVE-2022-38731 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38731 is a medium-severity path traversal vulnerability in n/a, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-38731 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-38731/ (Markdown: https://insights.sbomify.com/CVE-2022-38731/index.md)
```

## Sources

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

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