You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently tool have default 100 ports scan. So, we can add flag which runs top 1000 port scan.
Context
In many real-world scenarios, attackers or security professionals are looking for common vulnerabilities or services that might be exposed. By scanning the top 1000 ports, you are more likely to identify such issues efficiently.
Possible implementation
No response
Additional information
No response
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
This commit adds a new feature that allows users to perform a top 1000 port scan using the --top1000 flag. The top 1000 port scan covers the most commonly used ports for network scanning.
Changes include:
- Updated argparse to support the --top1000 flag.
- Modified port range for top 1000 scan.
- Added documentation for the new feature in the usage message.
th3cyb3rhub#36
The reference code above is just the first 1000 ports, but not the most common for vulnerability scan.
Like:
Port 3389 (Remote Desktop Protocol - RDP)
Port 1433 (Microsoft SQL Server)
Port 3306 (MySQL Database)
Port 8080 (Alternative HTTP port)
Port 2222 (Alternative SSH port)
Port 5900 (Virtual Network Computing - VNC)
Which not included in 1-1000 port scanner.
Tell me if I misunderstanding something here due to I new here.
Detailed description
Currently tool have default 100 ports scan. So, we can add flag which runs top 1000 port scan.
Context
In many real-world scenarios, attackers or security professionals are looking for common vulnerabilities or services that might be exposed. By scanning the top 1000 ports, you are more likely to identify such issues efficiently.
Possible implementation
No response
Additional information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: