With `[repository] FORCE_PRIVATE = true`, Gitea creates new repositories as private, but the post-receive hook still applied the `repo.private=false` push option to an empty repository created by push. Any user who can create repositories could make their new repository public in violation of the instance policy. The default configuration is not affected.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
Low
Partial data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Gitea Gitea
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
|
1.27.0
|
28.1.0
|
References 5
https://github.com/go-gitea/gitea/security/advisories/GHSA-fx95-gwfc-grgc
GitHub Security Advisory GHSA-fx95-gwfc-grgc
https://github.com/go-gitea/gitea/pull/39501
Fix: go-gitea/gitea pull request #39501
https://github.com/go-gitea/gitea/pull/39507
Fix backport to release/v28: go-gitea/gitea pull request #39507
https://blog.gitea.com/release-of-28.1.0/
Gitea 28.1.0 release announcement
https://github.com/go-gitea/gitea/releases/tag/v28.1.0
go-gitea/gitea v28.1.0 release