gitea remote command execution with default installation #2429

Closed
opened 2025-11-02 04:35:49 -06:00 by GiteaMirror · 5 comments
Owner

Originally created by @5alt on GitHub (Oct 22, 2018).

  • Gitea version (or commit ref): current (9458880c06)

  • Can you reproduce the bug at https://try.gitea.io:

    • Yes (provide example URL)
    • [ x] No
    • Not relevant

Description

Hi, I found a issue just like https://github.com/gogs/gogs/issues/5469.
With gitea's default installation, I can authenticate as arbitrary account. But due to some server configuration, I can't reproduce in https://try.gitea.io .

As this is a very severe issue, I won't post details here. Can you give me your email address and I send the details to you?

Originally created by @5alt on GitHub (Oct 22, 2018). - Gitea version (or commit ref): current (https://github.com/go-gitea/gitea/commit/9458880c068c985692a49caf608f0057c73790bf) - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ x] No - [ ] Not relevant ## Description Hi, I found a issue just like https://github.com/gogs/gogs/issues/5469. With gitea's default installation, I can authenticate as arbitrary account. But due to some server configuration, I can't reproduce in https://try.gitea.io . As this is a very severe issue, I won't post details here. Can you give me your email address and I send the details to you?
GiteaMirror added the topic/security label 2025-11-02 04:35:49 -06:00
Author
Owner

@techknowlogick commented on GitHub (Oct 22, 2018):

@5alt thanks for report, security@gitea.io is the email address.

@techknowlogick commented on GitHub (Oct 22, 2018): @5alt thanks for report, security@gitea.io is the email address.
Author
Owner

@bugreport0 commented on GitHub (Oct 23, 2018):

If there's an app.ini / external way to mitigate this issue before an official patch is out, it might be worth sharing early so we can harden our installation(s). I don't want to interfere with any project security policy, but eventually the patch/commit will be public anyway.

@bugreport0 commented on GitHub (Oct 23, 2018): If there's an `app.ini` / external way to mitigate this issue before an official patch is out, it might be worth sharing early so we can harden our installation(s). I don't want to interfere with any project security policy, but eventually the patch/commit will be public anyway.
Author
Owner

@techknowlogick commented on GitHub (Oct 23, 2018):

The remote execution could be mitigated by setting DISABLE_GIT_HOOKS to true, however the account takeover is still a significant issue.

@techknowlogick commented on GitHub (Oct 23, 2018): The remote execution could be mitigated by setting `DISABLE_GIT_HOOKS` to true, however the account takeover is still a significant issue.
Author
Owner

@bugreport0 commented on GitHub (Oct 23, 2018):

@techknowlogick thanks! Account takeover is significant, but being able to prevent remote code execution right now is a huge deal.

@bugreport0 commented on GitHub (Oct 23, 2018): @techknowlogick thanks! Account takeover is significant, but being able to prevent remote code execution right now is a huge deal.
Author
Owner

@5alt commented on GitHub (Oct 26, 2018):

https://github.com/gogs/gogs/issues/5469#issuecomment-433280865

@5alt commented on GitHub (Oct 26, 2018): https://github.com/gogs/gogs/issues/5469#issuecomment-433280865
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2429