-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
SessionProvider MySQL credentials are shown in the admin GUI as plaintext #7147
Closed
2 of 7 tasks
Labels
topic/security
Something leaks user information or is otherwise vulnerable. Should be fixed!
Milestone
Comments
zeripath
changed the title
MySQL credentials are shown in the GUI as plaintext
SessionProvider MySQL credentials are shown in the GUI as plaintext
Jun 6, 2019
zeripath
changed the title
SessionProvider MySQL credentials are shown in the GUI as plaintext
SessionProvider MySQL credentials are shown in the admin GUI as plaintext
Jun 6, 2019
lunny
added
the
topic/security
Something leaks user information or is otherwise vulnerable. Should be fixed!
label
Jun 8, 2019
@zeripath Well, now it shows nothing: But still better than showing credentials. |
Do you have/get any logs? |
No errors or strange logs in console, just usual router logs... I have the default gitea.log. Tell me if you need more. |
techknowlogick
pushed a commit
that referenced
this issue
Nov 29, 2019
… (#9203) * Properly fix #7147 Although #7300 properly shadows the password from the virtual session provider, the template displaying the provider config still presumed that the config was JSON. This PR updates the template and properly hides the Virtual Session provider. Fixes #7147 * update per @silverwind's suggestion
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
[x]
):Description
Greetings!
I'm using Gitea 1.8.1 with MySQL 5.7. And if I'm using MySQL for session storing purposes, I can see the credentials in GUI as plaintext.
Steps to reproduce
Screenshots
The text was updated successfully, but these errors were encountered: