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.
Analysis
No analysis available yet.
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
No data available yet.
Remediation
No remediation available yet.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
 EUVD |
EUVD-2022-6551 | 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. |
 Github GHSA |
GHSA-fhv8-m4j4-cww2 | Gitea allowed assignment of private issues |
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-03T10:45:52.995Z
Reserved: 2022-08-12T00:00:00.000Z
Link: CVE-2022-38183
Vulnrichment
No data.
NVD
Status : Modified
Published: 2022-08-12T20:15:09.940
Modified: 2024-11-21T07:15:57.377
Link: CVE-2022-38183
Redhat
No data.
OpenCVE Enrichment
No data.
Weaknesses