2024-03-06 14:17:52 +05:30
|
|
|
// Copyright 2024 The Gitea Authors. All rights reserved.
|
|
|
|
// SPDX-License-Identifier: MIT
|
|
|
|
|
|
|
|
package integration
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"net/url"
|
|
|
|
"testing"
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
"time"
|
2024-03-06 14:17:52 +05:30
|
|
|
|
|
|
|
"code.gitea.io/gitea/models/db"
|
|
|
|
git_model "code.gitea.io/gitea/models/git"
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
repo_model "code.gitea.io/gitea/models/repo"
|
2024-03-06 14:17:52 +05:30
|
|
|
"code.gitea.io/gitea/models/unittest"
|
|
|
|
user_model "code.gitea.io/gitea/models/user"
|
|
|
|
"code.gitea.io/gitea/modules/git"
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
"code.gitea.io/gitea/modules/log"
|
|
|
|
repo_module "code.gitea.io/gitea/modules/repository"
|
|
|
|
"code.gitea.io/gitea/modules/test"
|
2024-03-06 14:17:52 +05:30
|
|
|
repo_service "code.gitea.io/gitea/services/repository"
|
|
|
|
|
|
|
|
"github.com/stretchr/testify/assert"
|
|
|
|
"github.com/stretchr/testify/require"
|
|
|
|
)
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
func forEachObjectFormat(t *testing.T, f func(t *testing.T, objectFormat git.ObjectFormat)) {
|
|
|
|
for _, objectFormat := range []git.ObjectFormat{git.Sha256ObjectFormat, git.Sha1ObjectFormat} {
|
|
|
|
t.Run(objectFormat.Name(), func(t *testing.T) {
|
|
|
|
f(t, objectFormat)
|
|
|
|
})
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2024-03-06 14:17:52 +05:30
|
|
|
func TestGitPush(t *testing.T) {
|
|
|
|
onGiteaRun(t, testGitPush)
|
|
|
|
}
|
|
|
|
|
|
|
|
func testGitPush(t *testing.T, u *url.URL) {
|
2024-05-15 19:05:19 +05:30
|
|
|
forEachObjectFormat(t, func(t *testing.T, objectFormat git.ObjectFormat) {
|
|
|
|
t.Run("Push branches at once", func(t *testing.T) {
|
|
|
|
runTestGitPush(t, u, objectFormat, func(t *testing.T, gitPath string) (pushed, deleted []string) {
|
|
|
|
for i := 0; i < 100; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
pushed = append(pushed, branchName)
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
}
|
|
|
|
pushed = append(pushed, "master")
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "--all")(t)
|
|
|
|
return pushed, deleted
|
|
|
|
})
|
2024-03-06 14:17:52 +05:30
|
|
|
})
|
|
|
|
|
2024-05-29 12:13:02 +05:30
|
|
|
t.Run("Push branches exists", func(t *testing.T) {
|
|
|
|
runTestGitPush(t, u, objectFormat, func(t *testing.T, gitPath string) (pushed, deleted []string) {
|
|
|
|
for i := 0; i < 10; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
if i < 5 {
|
|
|
|
pushed = append(pushed, branchName)
|
|
|
|
}
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
}
|
|
|
|
// only push master and the first 5 branches
|
|
|
|
pushed = append(pushed, "master")
|
|
|
|
args := append([]string{"origin"}, pushed...)
|
|
|
|
doGitPushTestRepository(gitPath, args...)(t)
|
|
|
|
|
|
|
|
pushed = pushed[:0]
|
|
|
|
// do some changes for the first 5 branches created above
|
|
|
|
for i := 0; i < 5; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
pushed = append(pushed, branchName)
|
|
|
|
|
|
|
|
doGitAddSomeCommits(gitPath, branchName)(t)
|
|
|
|
}
|
|
|
|
|
|
|
|
for i := 5; i < 10; i++ {
|
|
|
|
pushed = append(pushed, fmt.Sprintf("branch-%d", i))
|
|
|
|
}
|
|
|
|
pushed = append(pushed, "master")
|
|
|
|
|
|
|
|
// push all, so that master are not chagned
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "--all")(t)
|
|
|
|
|
|
|
|
return pushed, deleted
|
|
|
|
})
|
|
|
|
})
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Push branches one by one", func(t *testing.T) {
|
|
|
|
runTestGitPush(t, u, objectFormat, func(t *testing.T, gitPath string) (pushed, deleted []string) {
|
|
|
|
for i := 0; i < 100; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", branchName)(t)
|
|
|
|
pushed = append(pushed, branchName)
|
|
|
|
}
|
|
|
|
return pushed, deleted
|
|
|
|
})
|
2024-03-06 14:17:52 +05:30
|
|
|
})
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Delete branches", func(t *testing.T) {
|
|
|
|
runTestGitPush(t, u, objectFormat, func(t *testing.T, gitPath string) (pushed, deleted []string) {
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "master")(t) // make sure master is the default branch instead of a branch we are going to delete
|
|
|
|
pushed = append(pushed, "master")
|
|
|
|
|
|
|
|
for i := 0; i < 100; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
pushed = append(pushed, branchName)
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
}
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "--all")(t)
|
|
|
|
|
|
|
|
for i := 0; i < 10; i++ {
|
|
|
|
branchName := fmt.Sprintf("branch-%d", i)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "--delete", branchName)(t)
|
|
|
|
deleted = append(deleted, branchName)
|
|
|
|
}
|
|
|
|
return pushed, deleted
|
|
|
|
})
|
2024-03-06 14:17:52 +05:30
|
|
|
})
|
2024-03-20 07:15:27 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Push to deleted branch", func(t *testing.T) {
|
|
|
|
runTestGitPush(t, u, objectFormat, func(t *testing.T, gitPath string) (pushed, deleted []string) {
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "master")(t) // make sure master is the default branch instead of a branch we are going to delete
|
|
|
|
pushed = append(pushed, "master")
|
2024-03-20 07:15:27 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
doGitCreateBranch(gitPath, "branch-1")(t)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "branch-1")(t)
|
|
|
|
pushed = append(pushed, "branch-1")
|
2024-03-20 07:15:27 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
// delete and restore
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "--delete", "branch-1")(t)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", "branch-1")(t)
|
2024-03-20 07:15:27 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
return pushed, deleted
|
|
|
|
})
|
2024-03-20 07:15:27 +05:30
|
|
|
})
|
|
|
|
})
|
2024-03-06 14:17:52 +05:30
|
|
|
}
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
func runTestGitPush(t *testing.T, u *url.URL, objectFormat git.ObjectFormat, gitOperation func(t *testing.T, gitPath string) (pushed, deleted []string)) {
|
2024-03-06 14:17:52 +05:30
|
|
|
user := unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2})
|
|
|
|
repo, err := repo_service.CreateRepository(db.DefaultContext, user, user, repo_service.CreateRepoOptions{
|
2024-05-15 19:05:19 +05:30
|
|
|
Name: "repo-to-push",
|
|
|
|
Description: "test git push",
|
|
|
|
AutoInit: false,
|
|
|
|
DefaultBranch: "main",
|
|
|
|
IsPrivate: false,
|
|
|
|
ObjectFormatName: objectFormat.Name(),
|
2024-03-06 14:17:52 +05:30
|
|
|
})
|
|
|
|
require.NoError(t, err)
|
|
|
|
require.NotEmpty(t, repo)
|
|
|
|
|
|
|
|
gitPath := t.TempDir()
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
doGitInitTestRepository(gitPath, objectFormat)(t)
|
2024-03-06 14:17:52 +05:30
|
|
|
|
|
|
|
oldPath := u.Path
|
|
|
|
oldUser := u.User
|
|
|
|
defer func() {
|
|
|
|
u.Path = oldPath
|
|
|
|
u.User = oldUser
|
|
|
|
}()
|
|
|
|
u.Path = repo.FullName() + ".git"
|
|
|
|
u.User = url.UserPassword(user.LowerName, userPassword)
|
|
|
|
|
|
|
|
doGitAddRemote(gitPath, "origin", u)(t)
|
|
|
|
|
|
|
|
gitRepo, err := git.OpenRepository(git.DefaultContext, gitPath)
|
|
|
|
require.NoError(t, err)
|
|
|
|
defer gitRepo.Close()
|
|
|
|
|
|
|
|
pushedBranches, deletedBranches := gitOperation(t, gitPath)
|
|
|
|
|
|
|
|
dbBranches := make([]*git_model.Branch, 0)
|
|
|
|
require.NoError(t, db.GetEngine(db.DefaultContext).Where("repo_id=?", repo.ID).Find(&dbBranches))
|
|
|
|
assert.Equalf(t, len(pushedBranches), len(dbBranches), "mismatched number of branches in db")
|
|
|
|
dbBranchesMap := make(map[string]*git_model.Branch, len(dbBranches))
|
|
|
|
for _, branch := range dbBranches {
|
|
|
|
dbBranchesMap[branch.Name] = branch
|
|
|
|
}
|
|
|
|
|
|
|
|
deletedBranchesMap := make(map[string]bool, len(deletedBranches))
|
|
|
|
for _, branchName := range deletedBranches {
|
|
|
|
deletedBranchesMap[branchName] = true
|
|
|
|
}
|
|
|
|
|
|
|
|
for _, branchName := range pushedBranches {
|
|
|
|
branch, ok := dbBranchesMap[branchName]
|
|
|
|
deleted := deletedBranchesMap[branchName]
|
|
|
|
assert.True(t, ok, "branch %s not found in database", branchName)
|
|
|
|
assert.Equal(t, deleted, branch.IsDeleted, "IsDeleted of %s is %v, but it's expected to be %v", branchName, branch.IsDeleted, deleted)
|
|
|
|
commitID, err := gitRepo.GetBranchCommitID(branchName)
|
|
|
|
require.NoError(t, err)
|
|
|
|
assert.Equal(t, commitID, branch.CommitID)
|
|
|
|
}
|
|
|
|
|
|
|
|
require.NoError(t, repo_service.DeleteRepositoryDirectly(db.DefaultContext, user, repo.ID))
|
|
|
|
}
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
|
|
|
func TestOptionsGitPush(t *testing.T) {
|
|
|
|
onGiteaRun(t, testOptionsGitPush)
|
|
|
|
}
|
|
|
|
|
|
|
|
func testOptionsGitPush(t *testing.T, u *url.URL) {
|
|
|
|
user := unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2})
|
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
forEachObjectFormat(t, func(t *testing.T, objectFormat git.ObjectFormat) {
|
|
|
|
repo, err := repo_service.CreateRepository(db.DefaultContext, user, user, repo_service.CreateRepoOptions{
|
|
|
|
Name: "repo-to-push",
|
|
|
|
Description: "test git push",
|
|
|
|
AutoInit: false,
|
|
|
|
DefaultBranch: "main",
|
|
|
|
IsPrivate: false,
|
|
|
|
ObjectFormatName: objectFormat.Name(),
|
|
|
|
})
|
|
|
|
require.NoError(t, err)
|
|
|
|
require.NotEmpty(t, repo)
|
|
|
|
|
|
|
|
gitPath := t.TempDir()
|
|
|
|
|
|
|
|
doGitInitTestRepository(gitPath, objectFormat)(t)
|
|
|
|
|
|
|
|
u.Path = repo.FullName() + ".git"
|
|
|
|
u.User = url.UserPassword(user.LowerName, userPassword)
|
|
|
|
doGitAddRemote(gitPath, "origin", u)(t)
|
|
|
|
|
|
|
|
t.Run("Unknown push options are rejected", func(t *testing.T) {
|
|
|
|
logChecker, cleanup := test.NewLogChecker(log.DEFAULT, log.TRACE)
|
|
|
|
logChecker.Filter("unknown option").StopMark("Git push options validation")
|
|
|
|
defer cleanup()
|
|
|
|
branchName := "branch0"
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepositoryFail(gitPath, "origin", branchName, "-o", "repo.template=false", "-o", "uknownoption=randomvalue")(t)
|
|
|
|
logFiltered, logStopped := logChecker.Check(5 * time.Second)
|
|
|
|
assert.True(t, logStopped)
|
|
|
|
assert.True(t, logFiltered[0])
|
|
|
|
})
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Owner sets private & template to true via push options", func(t *testing.T) {
|
|
|
|
branchName := "branch1"
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", branchName, "-o", "repo.private=true", "-o", "repo.template=true")(t)
|
|
|
|
repo, err := repo_model.GetRepositoryByOwnerAndName(db.DefaultContext, user.Name, "repo-to-push")
|
|
|
|
require.NoError(t, err)
|
|
|
|
require.True(t, repo.IsPrivate)
|
|
|
|
require.True(t, repo.IsTemplate)
|
|
|
|
})
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Owner sets private & template to false via push options", func(t *testing.T) {
|
|
|
|
branchName := "branch2"
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepository(gitPath, "origin", branchName, "-o", "repo.private=false", "-o", "repo.template=false")(t)
|
|
|
|
repo, err = repo_model.GetRepositoryByOwnerAndName(db.DefaultContext, user.Name, "repo-to-push")
|
|
|
|
require.NoError(t, err)
|
|
|
|
require.False(t, repo.IsPrivate)
|
|
|
|
require.False(t, repo.IsTemplate)
|
|
|
|
})
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
// create a collaborator with write access
|
|
|
|
collaborator := unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 5})
|
|
|
|
u.User = url.UserPassword(collaborator.LowerName, userPassword)
|
|
|
|
doGitAddRemote(gitPath, "collaborator", u)(t)
|
|
|
|
repo_module.AddCollaborator(db.DefaultContext, repo, collaborator)
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Collaborator with write access is allowed to push", func(t *testing.T) {
|
|
|
|
branchName := "branch3"
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepository(gitPath, "collaborator", branchName)(t)
|
|
|
|
})
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
t.Run("Collaborator with write access fails to change private & template via push options", func(t *testing.T) {
|
|
|
|
logChecker, cleanup := test.NewLogChecker(log.DEFAULT, log.TRACE)
|
|
|
|
logChecker.Filter("permission denied for changing repo settings").StopMark("Git push options validation")
|
|
|
|
defer cleanup()
|
|
|
|
branchName := "branch4"
|
|
|
|
doGitCreateBranch(gitPath, branchName)(t)
|
|
|
|
doGitPushTestRepositoryFail(gitPath, "collaborator", branchName, "-o", "repo.private=true", "-o", "repo.template=true")(t)
|
|
|
|
repo, err = repo_model.GetRepositoryByOwnerAndName(db.DefaultContext, user.Name, "repo-to-push")
|
|
|
|
require.NoError(t, err)
|
|
|
|
require.False(t, repo.IsPrivate)
|
|
|
|
require.False(t, repo.IsTemplate)
|
|
|
|
logFiltered, logStopped := logChecker.Check(5 * time.Second)
|
|
|
|
assert.True(t, logStopped)
|
|
|
|
assert.True(t, logFiltered[0])
|
|
|
|
})
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
|
2024-05-15 19:05:19 +05:30
|
|
|
require.NoError(t, repo_service.DeleteRepositoryDirectly(db.DefaultContext, user, repo.ID))
|
hooks: Harden when we accept push options that change repo settings
It is possible to change some repo settings (its visibility, and
template status) via `git push` options: `-o repo.private=true`, `-o
repo.template=true`.
Previously, there weren't sufficient permission checks on these, and
anyone who could `git push` to a repository - including via an AGit
workflow! - was able to change either of these settings. To guard
against this, the pre-receive hook will now check if either of these
options are present, and if so, will perform additional permission
checks to ensure that these can only be set by a repository owner or
an administrator. Additionally, changing these settings is disabled for
forks, even for the fork's owner.
There's still a case where the owner of a repository can change the
visibility of it, and it will not propagate to forks (it propagates to
forks when changing the visibility via the API), but that's an
inconsistency, not a security issue.
Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>
Signed-off-by: Earl Warren <contact@earl-warren.org>
2024-04-15 13:37:45 +05:30
|
|
|
})
|
|
|
|
}
|