CVE-2022-38183GHSA-FHV8-M4J4-CWW2BIT-GITEA-2022-38183GO-2024-2769
In Gitea before 1.16.9, it was possible for users to add existing issues to projects.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.16.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- n/a n/a
Version range not reported
- code.gitea.io/giteaGo
fixed in 1.16.9