T08 · Insecure Dependencies
- Location
SKILL.md:155- Finding
Unpinned External Container Executed with Host Networking
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 155–157
Vulnerability Type: Unpinned third-party container dependency with excessive network access
Risk Level: MediumVulnerable Code
bash docker pull wallarm/gotestwaf docker run --rm --network="host" -v ${PWD}/reports:/app/reports \ wallarm/gotestwaf --url=http://target-url --noEmailReportTechnical Analysis
The documented workflow pulls and executes
wallarm/gotestwafwithout specifying an immutable version or image digest. The effective executable payload can therefore change after this skill has been reviewed. A tag update, registry compromise, or publisher-account compromise could cause users to execute different code than expected.The container is also granted host-network access through
--network="host"and write access to${PWD}/reports. Host networking removes Docker's normal network namespace isolation, allowing processes inside the container to communicate directly with services reachable through the host network stack. The bind mount exposes the selected local report directory to container modification.The audited artifact contains only
SKILL.md; it does not include the source tree referenced by the build instructions. Consequently, the external image's implementation cannot be verified against local source in this artifact.Attack Path
- An attacker compromises the image publisher, registry account, build pipeline, or mutable image tag.
- The attacker publishes a modified
wallarm/gotestwafimage under the referenced tag. - A user follows the documented command and pulls the modified image.
- Docker executes the attacker-controlled image with host networking enabled.
- The malicious process enumerates or accesses host-reachable services and other network resources available from the host.
- The process reads or alters content available through the mounted
${PWD}/reportsdirectory.
Imp
...[truncated 740 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the reviewed container to an immutable digest:
bash docker pull wallarm/gotestwaf@sha256:<verified-digest> docker run --rm \ --network=<restricted-network> \ --mount type=bind,src="${PWD}/reports",dst=/app/reports \ wallarm/gotestwaf@sha256:<verified-digest> \ --url=http://target-url --noEmailReport - Verify the digest through a trusted release channel and validate available image signatures or attestations before execution.
- Replace
--network="host"with a dedicated, restricted Docker network. Permit access only to the authorized WAF test target. - Mount only a dedicated output directory with narrowly scoped host permissions. Do not expose unrelated or sensitive files.
- Run the container as a non-root user, drop unnecessary Linux capabilities, enable
no-new-privileges, and use a read-only root filesystem where compatible:bash --user <non-root-uid> \ --cap-drop=ALL \ --security-opt=no-new-privileges \ --read-only - Include the corresponding reviewed source code and reproducible build instructions in the package so the image can be independently verified.
- Pin the reviewed container to an immutable digest:
