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

> Authenticated attackers can download arbitrary DWG files from the server via path traversal in the DownloadDwg endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9x3c-69rg-65p6

## What is CVE-2022-27248?

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

### Official description

A directory traversal vulnerability in IdeaRE RefTree before 2021.09.17 allows remote authenticated users to download arbitrary .dwg files from a remote server by specifying an absolute or relative path when invoking the affected DownloadDwg endpoint. An attack uses the path field to CaddemServiceJS/CaddemService.svc/rest/DownloadDwg.

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

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

It affects 1 product.


Products: Idearespa Reftree.

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

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

## Is CVE-2022-27248 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-27249](https://insights.sbomify.com/CVE-2022-27249/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27248 is a medium-severity path traversal vulnerability in n/a, published on 3 Apr 2022. 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-27248 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-27248/ (Markdown: https://insights.sbomify.com/CVE-2022-27248/index.md)
```

## Sources

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

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