# CVE-2020-35850: Server-side request forgery in n/a

> An SSRF vulnerability in Cockpit allows attackers to make arbitrary requests from the server, potentially accessing internal resources.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3mxq-x62m-9mvp, OESA-2024-1552, OESA-2024-1660, OESA-2024-1661

## What is CVE-2020-35850?

CVE-2020-35850 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An SSRF issue was discovered in cockpit-project.org Cockpit 234. NOTE: this is unrelated to the Agentejo Cockpit product. NOTE: the vendor states "I don't think [it] is a big real-life issue.

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

## Which versions are affected by CVE-2020-35850?

It affects 1 product.


Products: Cockpit-Project Cockpit.

## How do I fix CVE-2020-35850?

Apply the vendor's patch.

## Is CVE-2020-35850 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-3698](https://insights.sbomify.com/CVE-2021-3698/): Security feature bypass in cockpit (high 7.5)
- [CVE-2019-3804](https://insights.sbomify.com/CVE-2019-3804/): Denial of service in cockpit (high 7.5)
- [CVE-2021-3660](https://insights.sbomify.com/CVE-2021-3660/): Cross-site request forgery in cockpit (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35850 and fix it if it is affected.

What it is: CVE-2020-35850 is a medium-severity server-side request forgery vulnerability in n/a, published on 30 Dec 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-35850 in the wild and no public exploit code.

Affected product: n/a. 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-2020-35850/ (Markdown: https://insights.sbomify.com/CVE-2020-35850/index.md)
```

## Sources

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

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