T08 · Insecure Dependencies
- Location
SKILL.md:45- Finding
Mutable and Unverified RustDesk Container Image
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 45-47
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code:
bash docker run --name rustdesk-server -d \ --network host \ rustdesk/rustdesk-server:latestTechnical Analysis
The documented deployment command uses the mutable
latestcontainer tag without pinning a reviewed version or immutable image digest. It also provides no image-signature, checksum, or provenance-verification step.Because the content referenced by
latestcan change after this Skill has been reviewed, users may subsequently execute a different container image than the one originally intended. If the publisher account, registry, build pipeline, or mutable tag is compromised, attacker-controlled code could be distributed through the otherwise legitimate-looking command.Attack Path
- An attacker compromises the image publisher, container registry account, or upstream build pipeline.
- The attacker publishes a malicious image under
rustdesk/rustdesk-server:latestor replaces the image associated with that tag. - A user follows the deployment command in
SKILL.md. - Docker retrieves the current unverified image represented by
latest. - Attacker-controlled code executes inside the container with Docker's default container capabilities and the host network access separately granted by the command.
Impact Assessment
Successful exploitation permits arbitrary code execution inside the deployed container. The resulting access is constrained by the container runtime but includes Docker's default capabilities and, in this command, direct use of the host network namespace. A malicious image could expose network listeners, communicate with external systems, probe host-local or internal network services, and abuse any resources or secrets made available to the container. No host filesystem mounts or explicit privileged mod ...[truncated 125 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
latestwith a reviewed release version and an immutable digest, such as:bash docker run --name rustdesk-server -d \ --network rustdesk-net \ rustdesk/rustdesk-server:<reviewed-version>@sha256:<verified-digest> - Verify the image digest against an authenticated vendor release channel before deployment.
- Use image-signature and provenance verification, such as Sigstore Cosign, if supported by the publisher.
- Document a controlled update process that reviews release notes, vulnerability reports, and digest changes before upgrading.
- Scan the pinned image with a container vulnerability scanner and reject images containing critical unresolved vulnerabilities.
- Avoid combining an unverified image with broad runtime permissions such as host networking.
- Replace
