Skip to content
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

Security of Konishi #7

Open
dwrolvink opened this issue Jan 12, 2019 · 3 comments
Open

Security of Konishi #7

dwrolvink opened this issue Jan 12, 2019 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@dwrolvink
Copy link
Contributor

In github, the system complains about insecure packages. In npm, there are complaints. If I look at how the password is plain text at the registration step, I'm internally complaining. And a /p/ user looked through the site and said that within minutes he found all kinds of vulnerabilities.

I'm reading up on security, but I'm just generally a noob in all tangent fields here. We need to fix a lot of this before we release an actual beta. Just making this issue so it's on everyone's radar.

If anyone want to do a scan and report the security issues (possibly with solutions how to fix it), that'd be great.

@dwrolvink dwrolvink added the help wanted Extra attention is needed label Jan 12, 2019
@X1Zeth2X
Copy link
Member

Lookup HTTPS.

@X1Zeth2X X1Zeth2X reopened this Sep 27, 2019
@SirTediousOfFoo
Copy link

One minor thing but since I ran into it right away I'll just throw it out there - When trying to log in with incorrect credentials you return an error that's too specific.
In the case of me inputting an e-mail address that isn't yet in the system you specifically return an error saying: "The email you have entered does not match any account." and using a correct address with a wrong password yields a: "Failed to log in, password may be incorrect." error.

This opens you up a bit to exposing user creds since I am able to tell if a person does indeed have an account on the page which in turn drastically reduces my attack time should I try doing something funny.

A better error is more general, along the lines of "The e-mail or password you entered is incorrect.". This makes the output more fuzzy and while it does slightly hinder ease-of-use for the end user it's a common practice.

I'll try to help out more on security but I'm also just learning about that stuff so it's going to be a fun ride.

@X1Zeth2X
Copy link
Member

X1Zeth2X commented Dec 1, 2019

We've discussed a similar issue before but the thing here is that an attacker can simply go to the registration page, fill out the details and check if that email is used or not. This is done for UX reasons. Ultimately it's still the backend's job to make sure that the security is tight. You can also use other tools to call the API endpoints to check if email is used etc.

The backend has a lot of room for improvement in terms of security and things in general. For the frontend, it's preventing XSS, CSRF, the usual stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants