T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:19- Finding
Unpinned Remote Code and Dependency Retrieval
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a dashboard deployment guide, but it asks users to run mutable third-party code and can expose local agent data publicly with weak default access controls.
Install only after reviewing or pinning the external Star-Office-UI code, changing the default password and join keys, and deciding whether memory-note display is safe. Avoid public tunneling unless strong access controls are added, and do not enter Gemini keys or prompts that may contain secrets unless third-party processing is acceptable.
SKILL.md:19Unpinned Remote Code and Dependency Retrieval
SKILL.md:76Known Default Password and Predictable Shared Join Keys
SKILL.md:127Potential Disclosure of Agent Memory Through Public Dashboard Exposure
The skill instructs the agent to clone and run code directly from an external GitHub repository (git clone, install dependencies, then execute app.py) without pinning a commit, verifying integrity, or reviewing the code. This creates a supply-chain and arbitrary code execution risk on the host, which is broader than simply configuring a local dashboard and could lead to system compromise if the repository or dependencies are malicious or later changed.
Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.
或使用后台运行:
nohup python3 app.py > /tmp/star-office.log 2>&1 &
The Gemini API setup explains how to send data to a third-party AI service but does not clearly warn that prompts, images, and related content may leave the local environment and be processed by an external provider. For a dashboard that may contain user-generated text or images, this can lead to unintentional disclosure of confidential or personal data.
The Cloudflare Tunnel step exposes the locally hosted service to the public internet, expanding access far beyond local-only deployment. Even if presented as optional, the instructions normalize public exposure without requiring authentication hardening, access restrictions, or confirmation that the user understands the risks, which could allow unauthorized access or discovery of sensitive content.
The skill describes creating a public URL but does not clearly warn that anyone with the link may reach the service, nor does it discuss privacy, indexing/discovery risk, or the possibility of exposing internal state and agent activity. Omitting these warnings can cause users to unintentionally publish a local dashboard containing sensitive operational or personal information.