github.com/Z4nzu/hackingtool
Submitted 8/4/2026, 10:25:55 AM · Status: ok
Risk grade
D
71 / 100
Findings
12
0 critical5 high5 medium2 low0 info0 on CISA KEV0ATT&CK
Showing 12 of 12 findings
Findings
- os.system() runs a string through the shell — command injection if any part is influenced by input. Use subprocess with an argv list. (Apache-2.0.)os.system() runs a string through the shell — command injection if any part is influenced by input. Use subprocess with an argv list. (Apache-2.0.)semgrepsrc/hackingtool/core.py:541
- subprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list ansubprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list and shell=False. (First-party socbox; Apache-2.0.)semgrepsrc/hackingtool/os_detect.py:130
- subprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list ansubprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list and shell=False. (First-party socbox; Apache-2.0.)semgrepsrc/hackingtool/core.py:102
- subprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list ansubprocess invoked through the shell (shell=True) or with a command string that is interpolated/concatenated/.split() instead of a fixed argv list — command injection risk. Pass a literal argv list and shell=False. (First-party socbox; Apache-2.0.)semgrepsrc/hackingtool/tools/tool_manager.py:27
- Image user should not be 'root'Running containers with 'root' user can lead to a container escape situation. It is a best practice to run containers as non-root users, which can be done by adding a 'USER' statement to the Dockerfile.trivyDockerfile:0
- Ensure that a user for the container has been createdEnsure that a user for the container has been created on /Dockerfile.checkovDockerfile:1
- Ensure that HEALTHCHECK instructions have been added to container imagesEnsure that HEALTHCHECK instructions have been added to container images on /Dockerfile.checkovDockerfile:1
- Ensure the base image uses a non latest version tagEnsure the base image uses a non latest version tag on /Dockerfile.FROMcheckovDockerfile:5
- Ensure top-level permissions are not set to write-allEnsure top-level permissions are not set to write-all on on(checks)checkov.github/workflows/checks.yml:0
- ':latest' tag usedWhen using a 'FROM' statement you should use a specific tag to avoid uncontrolled behavior when the image is updated.trivyDockerfile:5
- PyPI publish GitHub Action vulnerable to injectable expression expansions in action stepsgrype
- No HEALTHCHECK definedYou should add HEALTHCHECK instruction in your docker container images to perform the health check on running containers.trivyDockerfile:0
This report is public.