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

mysql-ip-filter #21

Open
freb opened this issue Mar 27, 2019 · 0 comments
Open

mysql-ip-filter #21

freb opened this issue Mar 27, 2019 · 0 comments

Comments

@freb
Copy link
Contributor

freb commented Mar 27, 2019

The only nmap output that will show you the response message from MySQL when it is using IP filtering is the mysql-enum script with debug -dd. You will see a message like:

NSE: [mysql-enum W:55afb8ea6778 1.1.1.1:3306] Trying sysadmin against 1.1.1.1:3306
NSOCK INFO [0.7040s] nsock_trace_handler_callback(): Callback: READ SUCCESS for EID 50 [1.1.1.1:3306] (75 bytes): G....j.Host '2.2.2.2' is not allowed to connect to this MySQL server

I like to flag this issue as a low because you still have communication with the database. Even though chance for exploitation is reduced, it isn't eliminated.

The plugin should make the basic connection, most likely emulating the functionality of mysql-enum, and look for the not allowed response. In that case, it should check if the target address is a public IP address, and then flag it as a vuln.

Its possible a generic script for all public database detection is warranted. However, I've only ever come accross mysql exposed and returning some sort of response. But we could gather database responses from each datbase target discovered and check for public ip.

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

No branches or pull requests

1 participant