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

Option -A breaks scan for opened 53/tcp port #2821

Open
overheavenlyshadows opened this issue Apr 25, 2024 · 4 comments
Open

Option -A breaks scan for opened 53/tcp port #2821

overheavenlyshadows opened this issue Apr 25, 2024 · 4 comments
Labels

Comments

@overheavenlyshadows
Copy link

overheavenlyshadows commented Apr 25, 2024

Describe the bug
When using option -A to scan opened 53/tcp port it goes to "Unexpected error in NSE_TYPE_READ callback. Error code: 50 (Network is down)"

To Reproduce
Scan any host with opened 53 port using macos sonoma 14.3.1 (arm)

Expected behavior
Scanned port.

Version info (please complete the following information):
Nmap version 7.94 ( https://nmap.org )
Platform: arm-apple-darwin23.2.0
Compiled with: liblua-5.4.6 openssl-3.2.1 libssh2-1.11.0 libz-1.2.12 libpcre2-10.43 nmap-libpcap-1.10.4 nmap-libdnet-1.12 ipv6
Compiled without:
Available nsock engines: kqueue poll select

Additional context
Initiating Connect Scan at 18:31
Scanning <target_host> (<target_ip>) [1 port]
Discovered open port 53/tcp on <target_ip>
Completed Connect Scan at 18:31, 0.00s elapsed (1 total ports)
Initiating Service scan at 18:31
Scanning 1 service on <target_host> (<target_ip>)
Unexpected error in NSE_TYPE_READ callback. Error code: 50 (Network is down)
QUITTING!

@fyodor
Copy link
Member

fyodor commented Apr 25, 2024

Thanks for the report. It looks like we need to handle ENETDOWN error code. @dmiller-nmap is working on it.

@overheavenlyshadows
Copy link
Author

@fyodor seems like it was fixed in 7.95

@fyodor
Copy link
Member

fyodor commented May 20, 2024

Thanks for the update @overheavenlyshadows. We haven't put in the code fix yet but you may not be receiving the "network is down" callback error for other reasons. We're still working on the permanent fix and hope to have it in the next Nmap release.

@fyodor
Copy link
Member

fyodor commented May 20, 2024

Also we discussed it in a meeting today and @dmiller-nmap noted that we should probably also adjust that function (servicescan_read_handler in service_scan.cc) to not quit on unexpected errors there

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

No branches or pull requests

2 participants