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

Werkzeug Security Issue #170

Open
vxnuke opened this issue Nov 9, 2016 · 2 comments
Open

Werkzeug Security Issue #170

vxnuke opened this issue Nov 9, 2016 · 2 comments

Comments

@vxnuke
Copy link

vxnuke commented Nov 9, 2016

Hi, I scan the Internet and gather information about Internet connected devices all over the world. I found that Werkzeug Console is enabled and not protected on multiple hosts running this software. If console is enabled by default you should disable console or upgrade and put pin protection on it as it leaves system vulnerable to exploitation. Another issue too is even if you have http basic authentication enabled(Login). You can still access console without authentication.

@albino1
Copy link

albino1 commented Nov 9, 2016

Good to know.

FWIW, there's probably nothing that can be done about it because this project is long abandoned. Most people are on a different fork, and even if it did get updated after years of being dormant, there's no auto-update mechanism, so the only way for someone to find out there was a fix is to come to the long dead Github page and discover it on their own :)

@vxnuke
Copy link
Author

vxnuke commented Nov 9, 2016

Haha ok lol

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants