# CVE-2021-22255: Server-side request forgery in Baserow

> Remote authenticated users can perform Server-Side Request Forgery to access internal network resources via URL file upload.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-h2jg-46xv-c74w

## What is CVE-2021-22255?

CVE-2021-22255 is a high-severity server-side request forgery vulnerability in Baserow, published on 20 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SSRF in URL file upload in Baserow <1.1.0 allows remote authenticated users to retrieve files from the internal server network exposed over HTTP by inserting an internal address.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Baserow Baserow.

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

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

## Is CVE-2021-22255 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-22255 is a high-severity server-side request forgery vulnerability in Baserow, published on 20 Aug 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-22255 in the wild and no public exploit code.

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

## Sources

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

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