# CVE-2019-25087: RamseyK httpserver URI ResourceHost.cpp getResource path traversal

> Remote attackers can exploit a path traversal vulnerability in the URI handler to read arbitrary files from the server.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 27 Dec 2022
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-7rf6-522q-9wq4

## What is CVE-2019-25087?

CVE-2019-25087 is a medium-severity path traversal vulnerability in RamseyK httpserver, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in RamseyK httpserver. It has been rated as critical. This issue affects the function ResourceHost::getResource of the file src/ResourceHost.cpp of the component URI Handler. The manipulation of the argument uri leads to path traversal: '../filedir'. The attack may be initiated remotely. The name of the patch is 1a0de56e4dafff9c2f9c8f6b130a764f7a50df52. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-216863.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-24 (Path Traversal: '../filedir')

## Which versions are affected by CVE-2019-25087?

It affects 1 product.


Products: Httpserver Project Httpserver.

## How do I fix CVE-2019-25087?

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

## Is CVE-2019-25087 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25087 and fix it if it is affected.

What it is: CVE-2019-25087 is a medium-severity path traversal vulnerability in RamseyK httpserver, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25087 in the wild and no public exploit code.

Affected product: RamseyK httpserver. 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-2019-25087/ (Markdown: https://insights.sbomify.com/CVE-2019-25087/index.md)
```

## Sources

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

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