[issue] Spam accounts gets created trough local account (no way?!) #13725

Closed
opened 2025-11-02 10:51:26 -06:00 by GiteaMirror · 11 comments
Owner

Originally created by @0n1cOn3 on GitHub (Nov 19, 2024).

Description

Spammers found a way to register an account without using the given Login Providers (as you can see from the screenshot below)

Gitea Version

1.22.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

image
image

Git Version

2.34.1

Operating System

Ubuntu 20.04 LTS

How are you running Gitea?

Docker-Compose V2

Database

MySQL/MariaDB

Originally created by @0n1cOn3 on GitHub (Nov 19, 2024). ### Description Spammers found a way to register an account without using the given Login Providers (as you can see from the screenshot below) ### Gitea Version 1.22.0 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots ![image](https://github.com/user-attachments/assets/4d933b53-0965-4ffa-961f-964a06feb395) ![image](https://github.com/user-attachments/assets/2228c71b-41cd-4ffa-90e7-c4786783fd01) ### Git Version 2.34.1 ### Operating System Ubuntu 20.04 LTS ### How are you running Gitea? Docker-Compose V2 ### Database MySQL/MariaDB
GiteaMirror added the issue/needs-feedbackissue/not-a-bug labels 2025-11-02 10:51:26 -06:00
Author
Owner

@lunny commented on GitHub (Nov 19, 2024):

You can enable captcha and other methods to avoid spammers. If you want to disable local user, it's duplicated of #13606

@lunny commented on GitHub (Nov 19, 2024): You can enable captcha and other methods to avoid spammers. If you want to disable local user, it's duplicated of #13606
Author
Owner

@0n1cOn3 commented on GitHub (Nov 19, 2024):

Thank you ! 🥇

@0n1cOn3 commented on GitHub (Nov 19, 2024): Thank you ! 🥇
Author
Owner

@0n1cOn3 commented on GitHub (Nov 19, 2024):

I have saddly to say, that Captcha is already enabled.
And the given thread from you is also saddly not really helpful to get that issue fixed :-(

@0n1cOn3 commented on GitHub (Nov 19, 2024): I have saddly to say, that Captcha is already enabled. And the given thread from you is also saddly not really helpful to get that issue fixed :-(
Author
Owner

@jiriks74 commented on GitHub (Nov 20, 2024):

I have saddly to say, that Captcha is already enabled.

I've enabled reCAPTCHA and verified that it appears on the registration website. Sadly it does nothing to stop the account spam I've been battling over the last few days.

@jiriks74 commented on GitHub (Nov 20, 2024): > I have saddly to say, that Captcha is already enabled. I've enabled reCAPTCHA and verified that it appears on the registration website. Sadly it does nothing to stop the account spam I've been battling over the last few days.
Author
Owner

@HashDot commented on GitHub (Dec 9, 2024):

I have had this problem for several weeks. I see 2 options for a quick but only temporary solution. You can disable the user registration completely and only invite users or you can set an e-mail restriction. But this does not help if you run a “public” instance. But for the Homelab this should solve the problems for now.

@HashDot commented on GitHub (Dec 9, 2024): I have had this problem for several weeks. I see 2 options for a quick but only temporary solution. You can disable the user registration completely and only invite users or you can set an e-mail restriction. But this does not help if you run a “public” instance. But for the Homelab this should solve the problems for now.
Author
Owner

@lunny commented on GitHub (Dec 10, 2024):

Disabling local user have been implemented in #32687 and will be released in v1.23.

@lunny commented on GitHub (Dec 10, 2024): Disabling local user have been implemented in #32687 and will be released in v1.23.
Author
Owner

@GiteaBot commented on GitHub (Jan 9, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Jan 9, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:
Author
Owner

@0n1cOn3 commented on GitHub (Jan 21, 2025):

Many thanks! @lunny

I have also seen through Wazuh that accounts are made through SQL injections. I really don't know how to prevent this exactly...

@0n1cOn3 commented on GitHub (Jan 21, 2025): Many thanks! @lunny I have also seen through Wazuh that accounts are made through SQL injections. I really don't know how to prevent this exactly...
Author
Owner

@lunny commented on GitHub (Jan 21, 2025):

Many thanks! @lunny

I have also seen through Wazuh that accounts are made through SQL injections. I really don't know how to prevent this exactly...

If you believe it's a security, please report it to security[at]gitea.io .

@lunny commented on GitHub (Jan 21, 2025): > Many thanks! [<img alt="" width="16" height="16" src="https://avatars.githubusercontent.com/u/81045?s=64&amp;u=99b64f0ca6ef63643c7583ab87dd31c52d28e673&amp;v=4">@lunny](https://github.com/lunny) > > I have also seen through Wazuh that accounts are made through SQL injections. I really don't know how to prevent this exactly... If you believe it's a security, please report it to security[at]gitea.io .
Author
Owner

@0n1cOn3 commented on GitHub (Jan 21, 2025):

Im gonna do that. Thx

@0n1cOn3 commented on GitHub (Jan 21, 2025): Im gonna do that. Thx
Author
Owner

@0n1cOn3 commented on GitHub (Jan 21, 2025):

Done - I'v send the mail a few minutes ago with an attachment.

@0n1cOn3 commented on GitHub (Jan 21, 2025): Done - I'v send the mail a few minutes ago with an attachment.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#13725