# CVE-2022-0870: Server-Side Request Forgery (SSRF) in gogs/gogs

> An attacker can exploit a Server-Side Request Forgery vulnerability in Gogs to access internal resources or bypass security controls.

- **Severity:** Medium 5.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/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:** Yes
- **Published:** 11 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** CLEANSTART-2024-SC73733, GHSA-7v5r-r995-q2x2, GO-2022-0566

## What is CVE-2022-0870?

CVE-2022-0870 is a medium-severity server-side request forgery vulnerability in gogs/gogs, published on 11 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) in GitHub repository gogs/gogs prior to 0.12.5.

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

## Which versions are affected by CVE-2022-0870?

3 open source packages ship an affected version, including gogs.io/gogs. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gogs.io/gogs` | Go | All versions | 0.12.5 |
| `gogs.io/gogs` | Go | All versions | 0.12.5 |
| `gogs.io/gogs` | Go | All versions | 0.12.5 |

Products: Gogs Gogs.

## How do I fix CVE-2022-0870?

Upgrade gogs.io/gogs to 0.12.5 or later.

## Is CVE-2022-0870 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0870 exists.

Public exploit code:

- Gogs <0.12.5 - Server-Side Request Forgery (nuclei): http/cves/2022/CVE-2022-0870.yaml

## Other vulnerabilities in gogs/gogs

- [CVE-2025-8110](https://insights.sbomify.com/CVE-2025-8110/): Gogs Path Traversal (high 8.7, exploited in the wild)
- [CVE-2024-56731](https://insights.sbomify.com/CVE-2024-56731/): Gogs deletion of internal files allows remote command execution (critical 10.0)
- [CVE-2022-1884](https://insights.sbomify.com/CVE-2022-1884/): Remote Command Execution in gogs/gogs (critical 10.0)
- [CVE-2022-1986](https://insights.sbomify.com/CVE-2022-1986/): OS Command Injection in gogs/gogs (critical 10.0)
- [CVE-2022-1992](https://insights.sbomify.com/CVE-2022-1992/): Path Traversal in gogs/gogs (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0870 and fix it if it is affected.

What it is: CVE-2022-0870 is a medium-severity server-side request forgery vulnerability in gogs/gogs, published on 11 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0870 exists.

Affected packages and fixed versions:
- gogs.io/gogs (Go): affected all versions; fixed in 0.12.5
- gogs.io/gogs (Go): affected all versions; fixed in 0.12.5
- gogs.io/gogs (Go): affected all versions; fixed in 0.12.5

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-2022-0870/ (Markdown: https://insights.sbomify.com/CVE-2022-0870/index.md)
```

## Sources

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

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