Moderate severityNVD Advisory· Published Aug 12, 2022· Updated Aug 3, 2024
CVE-2022-38183
CVE-2022-38183
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
code.gitea.io/giteaGo | < 1.16.9 | 1.16.9 |
Affected products
3- osv-coords2 versions
< 1.16.9+ 1 more
- (no CPE)range: < 1.16.9
- (no CPE)range: < 1.16.9
Patches
Vulnerability mechanics
References
10- github.com/advisories/GHSA-fhv8-m4j4-cww2ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2022-38183ghsaADVISORY
- security.gentoo.org/glsa/202210-14mitrevendor-advisory
- blog.gitea.io/2022/07/gitea-1.16.9-is-releasedghsaWEB
- github.com/go-gitea/gitea/pull/20133ghsaWEB
- github.com/go-gitea/gitea/pull/20196ghsaWEB
- herolab.usd.de/security-advisories/usd-2022-0015ghsaWEB
- pkg.go.dev/vuln/GO-2024-2769ghsaWEB
- blog.gitea.io/2022/07/gitea-1.16.9-is-released/mitre
- herolab.usd.de/security-advisories/usd-2022-0015/mitre
News mentions
0No linked articles in our index yet.