-
Updated
Nov 26, 2020 - Python
vulnerability-assessment
Here are 90 public repositories matching this topic...
-
Updated
Nov 26, 2020 - Go
-
Updated
Nov 23, 2020 - Shell
-
Updated
Jan 29, 2020 - Python
-
Updated
Mar 5, 2020 - Python
-
Updated
May 22, 2020 - Lua
-
Updated
Nov 26, 2020 - Python
-
Updated
Nov 23, 2020 - Python
-
Updated
Dec 24, 2019
-
Updated
Jun 12, 2020 - Python
-
Updated
Nov 26, 2020 - C
-
Updated
Nov 12, 2020 - Perl
-
Updated
Oct 11, 2020 - Python
-
Updated
Jul 1, 2020 - Java
-
Updated
Apr 22, 2018 - Python
-
Updated
Nov 12, 2020 - Ruby
-
Updated
Apr 20, 2020 - Python
-
Updated
Jul 18, 2018 - Python
-
Updated
Oct 2, 2020 - Python
-
Updated
Oct 30, 2020 - Python
-
Updated
Nov 13, 2020 - Python
-
Updated
Oct 18, 2018 - Go
-
Updated
Nov 26, 2020 - JavaScript
Elastic comes with quite a few security-related settings which seem easy enough to check for
https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html
Build an npm scanner
-
Updated
Nov 1, 2020 - TypeScript
-
Updated
Nov 23, 2020 - Python
-
Updated
Sep 29, 2017 - Lua
Improve this page
Add a description, image, and links to the vulnerability-assessment topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the vulnerability-assessment topic, visit your repo's landing page and select "manage topics."


What's the issue?
Overwritten test scenario, can be summarized and link to payload lists from other repos
How do we solve it?
Chop down the content to the required and needed information, link to payload lists instead of enumerating all possible usernames and passwords, provide further guidance on how to test.
If no one is up to handle it, I can take care of it