# GHSA-fr26-qjc8-mvjx: Possible route enumeration in production mode via RouteNotFoundError view in Vaadin 10, 11-14, and 15-19 > Attackers can enumerate application routes via crafted requests in production mode if no custom error handler is configured, exposing internal structure. - **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:** 13 Oct 2021 ## What is GHSA-fr26-qjc8-mvjx? GHSA-fr26-qjc8-mvjx is a vulnerability in com.vaadin:flow-server, published on 13 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Improper sanitization of path in default `RouteNotFoundError` view in `com.vaadin:flow-server` versions 1.0.0 through 1.0.14 (Vaadin 10.0.0 through 10.0.18), 1.1.0 prior to 2.0.0 (Vaadin 11 prior to 14), 2.0.0 through 2.6.1 (Vaadin 14.0.0 through 14.6.1), and 3.0.0 through 6.0.9 (Vaadin 15.0.0 through 19.0.8) allows network attacker to enumerate all available routes via crafted HTTP request when application is running in production mode and no custom handler for `NotFoundException` is provided. ## Which versions are affected by GHSA-fr26-qjc8-mvjx? 6 open source packages ship an affected version, including com.vaadin:flow-server. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `com.vaadin:flow-server` | Maven | From 1.0.0 | 1.0.15 | | `com.vaadin:flow-server` | Maven | From 1.0.0 | 1.0.15 | | `com.vaadin:flow-server` | Maven | From 1.1.0 | 2.6.2 | | `com.vaadin:flow-server` | Maven | From 1.1.0 | 2.6.2 | | `com.vaadin:flow-server` | Maven | From 3.0.0 | 6.0.10 | | `com.vaadin:flow-server` | Maven | From 3.0.0 | 6.0.10 | ## How do I fix GHSA-fr26-qjc8-mvjx? Upgrade com.vaadin:flow-server to a fixed version for your release line: 1.0.15, 2.6.2 or 6.0.10. ## Is GHSA-fr26-qjc8-mvjx being exploited? There is no known exploitation of GHSA-fr26-qjc8-mvjx in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-fr26-qjc8-mvjx and fix it if it is affected. What it is: GHSA-fr26-qjc8-mvjx is a vulnerability in com.vaadin:flow-server, published on 13 Oct 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-fr26-qjc8-mvjx in the wild and no public exploit code. Affected packages and fixed versions: - com.vaadin:flow-server (Maven): affected from 1.0.0; fixed in 1.0.15 - com.vaadin:flow-server (Maven): affected from 1.0.0; fixed in 1.0.15 - com.vaadin:flow-server (Maven): affected from 1.1.0; fixed in 2.6.2 - com.vaadin:flow-server (Maven): affected from 1.1.0; fixed in 2.6.2 - com.vaadin:flow-server (Maven): affected from 3.0.0; fixed in 6.0.10 - com.vaadin:flow-server (Maven): affected from 3.0.0; fixed in 6.0.10 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-fr26-qjc8-mvjx/ (Markdown: https://insights.sbomify.com/GHSA-fr26-qjc8-mvjx/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-fr26-qjc8-mvjx --- From sbomify Insights: https://insights.sbomify.com/GHSA-fr26-qjc8-mvjx/ Summaries are generated and may contain mistakes; the official description above is the record.