In Forgejo before 1.20.5-1, certain endpoints do not check whether an object belongs to a repository for which permissions are being checked. This allows remote attackers to read private issues, read private pull requests, delete issues, and perform other unauthorized actions.
References
Link | Resource |
---|---|
https://about.gitea.com/security | Not Applicable |
https://codeberg.org/forgejo/forgejo/src/branch/forgejo/RELEASE-NOTES.md | Release Notes Vendor Advisory |
https://forgejo.org/2023-11-release-v1-20-5-1/ | Release Notes Vendor Advisory |
https://github.com/gogs/gogs/security | Not Applicable |
Configurations
History
No history.
Information
Published : 2023-12-03 19:15
Updated : 2023-12-07 14:52
NVD link : CVE-2023-49946
Mitre link : CVE-2023-49946
CVE.ORG link : CVE-2023-49946
JSON object : View
Products Affected
forgejo
- forgejo
CWE
CWE-732
Incorrect Permission Assignment for Critical Resource