-
Notifications
You must be signed in to change notification settings - Fork 2k
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
A serious security bug in leancloud visitor counter [solved] #25
Comments
Where u want to discuss? Let's go in gitter at this weekend? |
you can add security DNS or host name in leancloud's Security settings?After setting up a Web security domain name, you can only call server resources through the JavaScript SDK under this domain name. |
I don't know what's the trouble and where is bug, but yes, if this is security bug, it must be of course fixed. |
@sli1989 that's not the problem |
Now i'm working on fixing it and have some progress |
Fixes are done with a plugin.Chinese doc is on the way. English doc may be released in few days. |
Implemented in #137 pull. |
bug fixed in #137 . |
Is there any problems? It's too much setting steps...
|
@sli1989 please tell me what's ur node version and hexo version |
|
I meet the same problem as sli1989, and my node version is v6.10.0 . |
There are some not actually maked to production things:
So, i suggest for now it's beta feature and i make some changes in this commit (by default |
could u do this?i have no access to computer now |
Solved. All future reports for this plugin can be posted here. |
I agree and want to create new issue
I've found a very serious bug in the integrated leancloud visitor counter.
Using this bug, anyone can change the visitor data of the blogs that don't belong to him, and even have the ability to ruin other's whole database.
Steps to reproduce the behavior
I'm really not sure if i should write the reproduce steps here.
Need discussions. @ivan-nginx
NexT Version: 6.0.0 and those integrated with leancloud visitor counter
NexT Scheme:
All schemes
The text was updated successfully, but these errors were encountered: