# GHSA-cgjv-rghq-qhgp: Path Traversal in algo-httpserv

> Attackers can read arbitrary server files via path traversal in the algo-httpserv library due to insufficient input sanitization.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Sep 2019

## What is GHSA-cgjv-rghq-qhgp?

GHSA-cgjv-rghq-qhgp is a path traversal vulnerability in algo-httpserv, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `algo-httpserv` prior to 1.1.2 are vulnerable to Path Traversal.  Due to insufficient input sanitization, attackers can access server files by using relative paths. 

## Recommendation

Upgrade to version 1.1.2 or later.

## Which versions are affected by GHSA-cgjv-rghq-qhgp?

2 open source packages ship an affected version, including algo-httpserv.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `algo-httpserv` | npm | All versions | 1.1.2 |
| `algo-httpserv` | npm | All versions | 1.1.2 |

## How do I fix GHSA-cgjv-rghq-qhgp?

Upgrade algo-httpserv to 1.1.2 or later.

## Is GHSA-cgjv-rghq-qhgp being exploited?

There is no known exploitation of GHSA-cgjv-rghq-qhgp in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-cgjv-rghq-qhgp and fix it if it is affected.

What it is: GHSA-cgjv-rghq-qhgp is a path traversal vulnerability in algo-httpserv, published on 11 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-cgjv-rghq-qhgp in the wild and no public exploit code.

Affected packages and fixed versions:
- algo-httpserv (npm): affected all versions; fixed in 1.1.2
- algo-httpserv (npm): affected all versions; fixed in 1.1.2

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/GHSA-cgjv-rghq-qhgp/ (Markdown: https://insights.sbomify.com/GHSA-cgjv-rghq-qhgp/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-cgjv-rghq-qhgp

---
From sbomify Insights: https://insights.sbomify.com/GHSA-cgjv-rghq-qhgp/
Summaries are generated and may contain mistakes; the official description above is the record.