# CVE-2021-31410: Project sources exposure in Vaadin Designer

> Remote attackers can access project source code due to overly relaxed frontend resource server configuration in Vaadin Designer.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** 23 Apr 2021
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-42g8-5x99-8wwm

## What is CVE-2021-31410?

CVE-2021-31410 is a high-severity vulnerability in Vaadin Designer, published on 23 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Overly relaxed configuration of frontend resources server in Vaadin Designer versions 4.3.0 through 4.6.3 allows remote attackers to access project sources via crafted HTTP request.

Weakness: CWE-668 (Exposure of Resource to Wrong Sphere), CWE-402 (Transmission of Private Resources into a New Sphere)

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

It affects 1 product.


Products: Vaadin Designer.

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

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

## Is CVE-2021-31410 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-31410 is a high-severity vulnerability in Vaadin Designer, published on 23 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 CVE-2021-31410 in the wild and no public exploit code.

Affected product: Vaadin Designer. 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-31410/ (Markdown: https://insights.sbomify.com/CVE-2021-31410/index.md)
```

## Sources

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

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