-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remote Code Execution #5569
Comments
Is this responsible disclosure? |
@jhabdas, I didn't know that Gitea and Gogs were sharing the same code base until I learnt a bit more about the projects and the schism. Once I learnt about it, I thought I should give you guys a heads-up. |
@snyff could you send some detail to security at gitea.io ? |
sent! |
@snyff thanks for the report. You will be thanked officially in the release blog post, and we appreciate your report 😄 |
@techknowlogick: thanks for that! Can you thank "@PentesterLab" or "Louis from PentesterLab (pentesterlab.com)" for example instead of snyff. |
@snyff sounds good. The blog post PR is here: https://github.com/go-gitea/blog/pull/82/files#diff-e0f59ce8bb7e55f0518fc0ecafac06d7 is that suitable, or would you prefer something else. |
That's perfect! |
The vulnerability impacting Gogs also impacts gitea
gogs/gogs#5558
Gitea version (or commit ref): 8dc09ed
Can you reproduce the bug at https://try.gitea.io:
Description
By using upload file with a malicious filename, an attacker is able to become any users and then gain code execution using hooks.
Gogs already worked on the issue in their develop branch
Screenshots
Me logged in as user_id 1
The text was updated successfully, but these errors were encountered: