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
Link | Resource |
---|---|
https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/ | Release Notes Vendor Advisory |
https://herolab.usd.de/security-advisories/usd-2022-0015/ | Broken Link |
https://security.gentoo.org/glsa/202210-14 | Third Party Advisory |
https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/ | Release Notes Vendor Advisory |
https://herolab.usd.de/security-advisories/usd-2022-0015/ | Broken Link |
https://security.gentoo.org/glsa/202210-14 | Third Party Advisory |
Configurations
History
21 Nov 2024, 07:15
Type | Values Removed | Values Added |
---|---|---|
References | () https://blog.gitea.io/2022/07/gitea-1.16.9-is-released/ - Release Notes, Vendor Advisory | |
References | () https://herolab.usd.de/security-advisories/usd-2022-0015/ - Broken Link | |
References | () https://security.gentoo.org/glsa/202210-14 - Third Party Advisory |
08 Aug 2023, 14:22
Type | Values Removed | Values Added |
---|---|---|
CWE | CWE-862 |
Information
Published : 2022-08-12 20:15
Updated : 2024-11-21 07:15
NVD link : CVE-2022-38183
Mitre link : CVE-2022-38183
CVE.ORG link : CVE-2022-38183
JSON object : View
Products Affected
gitea
- gitea
CWE
CWE-862
Missing Authorization