# CVE-2021-45027: Path traversal in n/a

> An attacker can download arbitrary files from the Oliver v5 Library Server via unsanitized input in the FileServlet function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Sep 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pgpm-vjm2-c33c

## What is CVE-2021-45027?

CVE-2021-45027 is a high-severity path traversal vulnerability in n/a, published on 1 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An arbitrary file download vulnerability in Oliver v5 Library Server Versions < 5.00.008.053 via the FileServlet function allows for arbitrary file download by an attacker using unsanitized user supplied input.

Weakness: CWE-494 (Download of Code Without Integrity Check)

## Which versions are affected by CVE-2021-45027?

It affects 1 product.


Products: Softlinkint Oliver V5 Library.

## How do I fix CVE-2021-45027?

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

## Is CVE-2021-45027 being exploited?

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

Public exploit code:

- Oliver 5 Library Server <8.00.008.053 - Local File Inclusion (nuclei): http/cves/2021/CVE-2021-45027.yaml

## Other vulnerabilities in n/a

- [CVE-2021-47755](https://insights.sbomify.com/CVE-2021-47755/): Oliver Library Server v5 - Arbitrary File Download (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45027 and fix it if it is affected.

What it is: CVE-2021-45027 is a high-severity path traversal vulnerability in n/a, published on 1 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-45027 exists.

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

## Sources

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

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