OWASP / OWASP/Nettacker

Same 3 Ports and Never ANY Results

Open
#817 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

answered question
Dominant language
Python
Stars
5.6k
Forks
1.2k
Avg merge
1d 21h
Merged PRs (30d)
16

Description

Maybe it's because I'm new to bug bounty hunting/pentesting, but no matter what I do, I seem to get the same ports scanned with no results to show in the report. I have tried the following modules to no success (my screenshot here shows 1 example of its failure):

subdomain_scan
subdomain_takeover_vuln
admin_scan
wordpress_version_scan

What am I missing or doing wrong? How do I use this tool correctly, or is it currently just broken?

Because after completing the scan shown in the photograph, the report showed nothing of value (to my knowledge anyway) and almost no information altogether.

{"timeout": 3.0, "host": "arkoselabs.com", "ports": "443", "method": "tcp_connect_send_and_receive", "response": {"ssl_flag": false, "conditions_results": {"http": ["HTTP/1.1 400", "Content-Length: 915", "Content-Type: ", "Server: "]}}}

That's as much as I figured out from the wordpress_version_scan report ^


OS: Kali Linux

OS Version: kali-linux-2023.4

Python Version: 3.11.8

nettacker_fail

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the scan against arkoselabs.com with the listed modules and the reported port 443 behavior. Compare the generated report with the module output and inspect the scanner's port and result handling to determine whether this is expected or a failure. Done means identifying a reproducible cause and documenting or correcting the missing results.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.