github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 02:24:21 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Token for trigger mirror-sync only #6361

New Issue
Closed
opened 2025-11-02 06:53:35 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 06:53:35 -06:00
Owner
Copy Link

Originally created by @wenerme on GitHub (Nov 20, 2020).

  • Gitea version (or commit ref): 1.14.0+dev-239-gad2a28862

  • Git version: 1.14.0+dev

  • Operating system: Linux/Docker

  • Database (use [x]):

    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite

Description

User can read repo, but can not trigger https://git.my.org/api/v1/repos/my/repo/mirror-sync?token=$TOKEN, this is used in the webhook of other system like gitlab, github. Webhook is not hide in most system, this cause the owner's PAT is leaked to who can access the webhook, which is quite common allowed a lot user to access. Better to have a token only for mirror-sync or provide another webhook url which not require token.

BTW, gitlab has a lot token for various actions, like feed token or email token, this can prevent leak the pat.

Originally created by @wenerme on GitHub (Nov 20, 2020). <!-- NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue --> <!-- 1. Please speak English, this is the language all maintainers can speak and write. 2. Please ask questions or configuration/deploy problems on our Discord server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 3. Please take a moment to check that your issue doesn't already exist. 4. Please give all relevant information below for bug reports, because incomplete details will be handled as an invalid report. --> - Gitea version (or commit ref): 1.14.0+dev-239-gad2a28862 - Git version: 1.14.0+dev - Operating system: Linux/Docker <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [X] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite ## Description User can read repo, but can not trigger `https://git.my.org/api/v1/repos/my/repo/mirror-sync?token=$TOKEN`, this is used in the webhook of other system like gitlab, github. Webhook is not hide in most system, this cause the owner's PAT is leaked to who can access the webhook, which is quite common allowed a lot user to access. Better to have a token only for `mirror-sync` or provide another webhook url which not require token. BTW, gitlab has a lot token for various actions, like feed token or email token, this can prevent leak the pat.
GiteaMirror added the issue/duplicate label 2025-11-02 06:53:35 -06:00
GiteaMirror commented 2025-11-02 06:53:35 -06:00
Author
Owner
Copy Link

@jolheiser commented on GitHub (Nov 20, 2020):

I think this is closely enough related to #4300 to close this one in favor of the other with more details.

@jolheiser commented on GitHub (Nov 20, 2020): I think this is closely enough related to #4300 to close this one in favor of the other with more details.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6361
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?