# GHSA-82mf-mmh7-hxp5: Directory traversal in development mode handler in Vaadin 14 and 15-17

> Attackers can read arbitrary files outside the intended folder via path traversal in Vaadin's development mode handler.

- **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:** 19 Apr 2021

## What is GHSA-82mf-mmh7-hxp5?

GHSA-82mf-mmh7-hxp5 is a path traversal vulnerability in com.vaadin:vaadin-bom, published on 19 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper URL validation in development mode handler in `com.vaadin:flow-server` versions 2.0.0 through 2.4.1 (Vaadin 14.0.0 through 14.4.2), and 3.0 prior to 5.0 (Vaadin 15 prior to 18) allows attacker to request arbitrary files stored outside of intended frontend resources folder.

- https://vaadin.com/security/cve-2020-36321

## Which versions are affected by GHSA-82mf-mmh7-hxp5?

4 open source packages ship an affected version, including com.vaadin:vaadin-bom.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.vaadin:vaadin-bom` | Maven | From 14.0.0 | 14.4.3 |
| `com.vaadin:vaadin-bom` | Maven | From 14.0.0 | 14.4.3 |
| `com.vaadin:vaadin-bom` | Maven | From 15.0.0 | 18.0.0 |
| `com.vaadin:vaadin-bom` | Maven | From 15.0.0 | 18.0.0 |

## How do I fix GHSA-82mf-mmh7-hxp5?

Upgrade com.vaadin:vaadin-bom to a fixed version for your release line: 14.4.3 or 18.0.0.

## Is GHSA-82mf-mmh7-hxp5 being exploited?

There is no known exploitation of GHSA-82mf-mmh7-hxp5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-82mf-mmh7-hxp5 and fix it if it is affected.

What it is: GHSA-82mf-mmh7-hxp5 is a path traversal vulnerability in com.vaadin:vaadin-bom, published on 19 Apr 2021. 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-82mf-mmh7-hxp5 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.vaadin:vaadin-bom (Maven): affected from 14.0.0; fixed in 14.4.3
- com.vaadin:vaadin-bom (Maven): affected from 14.0.0; fixed in 14.4.3
- com.vaadin:vaadin-bom (Maven): affected from 15.0.0; fixed in 18.0.0
- com.vaadin:vaadin-bom (Maven): affected from 15.0.0; fixed in 18.0.0

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-82mf-mmh7-hxp5/ (Markdown: https://insights.sbomify.com/GHSA-82mf-mmh7-hxp5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-82mf-mmh7-hxp5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-82mf-mmh7-hxp5/
Summaries are generated and may contain mistakes; the official description above is the record.