# CVE-2021-3382: Buffer Overflow in gitea

> Remote attackers can crash the Gitea service via a stack buffer overflow triggered by malicious file paths.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Feb 2021
- **Updated:** 3 Aug 2024
- **Also known as:** BIT-gitea-2021-3382, CLEANSTART-2025-DZ77580, GHSA-9f8c-pfvv-p4gm, GO-2024-2757

## What is CVE-2021-3382?

CVE-2021-3382 is a high-severity memory corruption vulnerability in Gitea Gitea, published on 5 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Stack buffer overflow vulnerability in gitea 1.9.0 through 1.13.1 allows remote attackers to cause a denial of service (crash) via vectors related to a file path.

Weakness: CWE-787 (Out-of-bounds Write)

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

4 open source packages ship an affected version, including github.com/go-gitea/gitea, gitea and code.gitea.io/gitea. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/go-gitea/gitea` | Go | From 1.9.0 | 1.13.2 |
| `github.com/go-gitea/gitea` | Go | From 1.9.0 | 1.13.2 |
| `gitea` | Bitnami | From 1.9.0 | 1.13.2 |
| `code.gitea.io/gitea` | Go | From 1.9.0 | 1.13.2 |

Products: Gitea Gitea.

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

Upgrade github.com/go-gitea/gitea to 1.13.2 or later.

## Is CVE-2021-3382 being exploited?

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

## Other vulnerabilities in Gitea Gitea

- [CVE-2026-60004](https://insights.sbomify.com/CVE-2026-60004/): Gitea Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-73278](https://insights.sbomify.com/CVE-2026-73278/): Gitea WebAuthn bypass during OAuth and OIDC sign-in (critical 9.8)
- [CVE-2026-94205](https://insights.sbomify.com/CVE-2026-94205/): Gitea fork workflow approval bypass through maintainer-triggered events (critical 9.8)
- [CVE-2022-42968](https://insights.sbomify.com/CVE-2022-42968/): Gitea vulnerable to Argument Injection (critical 9.8)
- [CVE-2021-45330](https://insights.sbomify.com/CVE-2021-45330/): Improper Privilege Management in Gitea (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-3382 is a high-severity memory corruption vulnerability in Gitea Gitea, published on 5 Feb 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-3382 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/go-gitea/gitea (Go): affected from 1.9.0; fixed in 1.13.2
- github.com/go-gitea/gitea (Go): affected from 1.9.0; fixed in 1.13.2
- gitea (Bitnami): affected from 1.9.0; fixed in 1.13.2
- code.gitea.io/gitea (Go): affected from 1.9.0; fixed in 1.13.2

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

## Sources

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

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