Описание
Gitea allowed assignment of private issues
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2022-38183
- https://github.com/go-gitea/gitea/pull/20133
- https://github.com/go-gitea/gitea/pull/20196
- https://blog.gitea.io/2022/07/gitea-1.16.9-is-released
- https://github.com/advisories/GHSA-fhv8-m4j4-cww2
- https://herolab.usd.de/security-advisories/usd-2022-0015
- https://pkg.go.dev/vuln/GO-2024-2769
Пакеты
code.gitea.io/gitea
< 1.16.9
1.16.9
Связанные уязвимости
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.
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.
In Gitea before 1.16.9, it was possible for users to add existing issu ...