Error: Unable to scan YOUR_HOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed

TL;DR

For "Unable to scan YOUR_HOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed.": move your app off the kernel port and rerun the scan. Please use a permitted port 1024..65535 to proceed.

Unable to scan YOUR_HOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed.

Steps

1. Per StackHawk's troubleshooting guide: the scan runs in an unprivileged container, so YOUR_HOST scans must target a permitted port (1024-65535). Move your app off the kernel port and rerun the scan.
2. Also searched as: "Unable to scan YOUR_HOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed."

When to use

You are seeing this: Per StackHawk's troubleshooting guide: the scan runs in an unprivileged container, so YOURHOST scans must target a permitted port (1024-65535). Use this skill when you run into "Error: Unable to scan YOURHOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

• Also searched as: "Unable to scan YOUR_HOST on ports 0..1023.

Source: Problem: A HawkScan run against a local app fails with: Error: Unable to scan YOURHOST on ports 0..1023. Please use a permitted port 1024..65535 to proceed. Cause: HawkScan reports this error when a kernel port (0..1023) is set for a scan against YOURHOST. HawkScan runs in an unprivileged container, which only provides permissions for the userland context, so scans against YOURHOST must use a permitted ephemeral port (1024-65535). Fix: point the scan at a permitted port, e.g. run the app on port 8080 and set host to YOURHOST (port 8080) in stackhawk.yml, then rerun hawk scan. If the scanner still cannot reach the app on YOUR_HOST, add --network=host to the docker run command.

Verified resolution: Per StackHawk's troubleshooting guide: the scan runs in an unprivileged container, so YOUR_HOST scans must target a permitted port (1024-65535). Move your app off the kernel port and rerun the scan.

Source URL: https://docs.stackhawk.com/hawkscan/troubleshooting/