Amass Scanner Scan fails #1826
Description
🐞 Bug report
Describe the bug
The amass scanner fails to execute. In the container logs, one can see an error. No file is written, so consequently, the parser fails as well.
Steps To Reproduce
Steps to reproduce the behavior:
- Install latest amass image with
helm upgrade --install amass secureCodeBox/amass - Submit example scan with
kubectl apply -f scanners/amass/examples/secureCodeBox.io/scan.yaml - In the logs of
caffix/amass:v4.0.3inscan-amass-securecodebox.io-...you see the errorflag provided but not defined: -json
Expected behavior
The amass container performs a scan
System (please complete the following information):
- secureCodeBox Version/Release: 4.0.1 (operator)
- OS: Ubuntu 20.04 (on WSL)
- Kubernetes Version: v1.27.4
- Docker Version: 24.0.4, build 3713ee1
Logs
Scanner
flag provided but not defined: -json
Stream closed EOF for default/scan-amass-securecodebox.io-c5sq9-bjqzz (amass)
Lurker
2023/07/24 11:23:58 Starting lurker
2023/07/24 11:23:58 Waiting for main container 'amass' to complete
2023/07/24 11:23:58 After scan is completed file '/home/securecodebox/amass-results.jsonl' will be uploaded to 'securecodebox-operator-minio.securecodebox-system.svc.cluster.local'
2023/07/24 11:23:58 Waiting for maincontainer to exit
2023/07/24 11:23:58 Main Container exited. Lurker will end as well.
2023/07/24 11:23:58 Uploading result files.
2023/07/24 11:23:58 Uploading /home/securecodebox/amass-results.jsonl
2023/07/24 11:23:58 File has a size of 0 bytes
2023/07/24 11:23:58 Failed to read file
2023/07/24 11:23:58 open /home/securecodebox/amass-results.jsonl: no such file or directory
Stream closed EOF for default/scan-amass-securecodebox.io-c5sq9-bjqzz (lurker)