Vulnerability advisory

CVE-2022-38183

Published Updated OSV record ↗

Also known as BIT-gitea-2022-38183GHSA-fhv8-m4j4-cww2GO-2024-2769

Severity

Severity not reported.

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/go-gitea/gitea ↗
All commits before 713bc6c8dca072c3946e5ff1ab6b1c58748f1a1a713bc6c8dca072c3946e5ff1ab6b1c58748f1a1a
Also listed as affected (31)
  • v1.16.8
  • v1.16.7
  • v1.16.6
  • v1.16.5
  • v1.16.4
  • v1.16.3
  • v1.16.2
  • v1.16.1
  • v1.16.0
  • v1.16.0-rc1
  • v1.15.0-rc1
  • v1.16.0-dev
  • v1.15.0-dev
  • v1.14.0-dev
  • v1.13.0-dev
  • v1.12.0-dev
  • v1.10.5
  • v1.11.0-rc1
  • v1.10.0-rc1
  • v1.11.0-dev
  • v1.9.0-rc1
  • v1.10.0-dev
  • v1.9.0-dev
  • v1.7.0-dev
  • v1.6.0-rc1
  • v1.6.0-dev
  • v1.5.0-rc1
  • v1.5.0-dev
  • v1.1.0
  • v1.0.0
  • v0.9.99

Description

In Gitea before 1.16.9, it was possible for users to add existing issues to projects. Due to improper access controls, an attacker could assign any issue to any project in Gitea (there was no permission check for fetching the issue). As a result, the attacker would get access to private issue titles.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools