Back to Database
Status published
Medium
CVE-2022-38183
In Gitea before 1.16.9, it was possible for users to...
Vulnerability 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.
Impact Analysis
Refer to official advisory for detailed impact metrics.
Remediation
Ensure systems are updated to the latest vendor-supplied patch levels.
THREAT MONITOR
Am I Vulnerable?
Launch our assessment wizard to check if your infrastructure is exposed to • CVE-2022-38183
Credits & Attribution
No credits recorded in the NVD database.
References
More from gitea
View All →CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in...
Unknown
0
CVE-2022-38795
In Gitea through 1.17.1, repo cloning can occur in the...
Medium
6.5
CVE-2022-30781
Gitea before 1.16.7 does not escape git fetch remote....
High
7.5
CVE-2022-27313
An arbitrary file deletion vulnerability in Gitea v1.16.3 allows attackers...
High
7.5
CVE-2021-45331
An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which...
Critical
9.8
Affected Vendor
gitea
View all reports →Affected Software
gitea
Vulnerable Versions:
0
Timeline
Official Publish:
August 12th, 2022
Last Modified:
August 3rd, 2024
Added to House:
July 21st, 2026
CVSS Vectors
V3:
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Weaknesses (CWE)
No CWE data available
MITRE ATT&CK TTPs
No associated TTPs found for this vulnerability.