T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:14- Finding
Documentation-Only Skill Requests Unnecessary Sensitive Credentials
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:14-22
Vulnerability Type: Violation of least privilege through excessive credential requirements
Risk Level: MediumVulnerable Code
yaml credentials: [GITHUB_TOKEN, WALLET_ADDRESS, DASHBOARD_SECRET] metadata: openclaw: requires: env: - GITHUB_TOKEN - WALLET_ADDRESS - DASHBOARD_SECRET primaryEnv: GITHUB_TOKENTechnical Analysis
The Skill declares itself to be a non-executable educational guide with
executable: falseandinstall: none. Its notice also states that the documented sandbox requires no API key. Despite this, the metadata requires the host to provide a GitHub personal access token and an administrative dashboard secret when the Skill is loaded.These credentials are not necessary to read or use the guide. Requiring them therefore violates least privilege by expanding the Skill's credential exposure beyond its declared runtime needs. Designating
GITHUB_TOKENasprimaryEnvfurther increases the likelihood that a sensitive repository token will be provisioned by default.The guide later describes legitimate, optional deployment-time uses for these values: fetching paid content from a private GitHub repository and authenticating to a storefront's administrative API. Those optional operations do not justify requiring the credentials for the documentation-only Skill itself.
No executable source or script is present in the audited package, so the audit found no evidence that the current artifact actively reads or exfiltrates these credentials. The finding concerns unnecessary credential provisioning and the resulting access surface, rather than confirmed credential theft.
Attack Path
- A user installs or loads the Skill to consult its educational content.
- The host processes the
metadata.openclaw.requires.envdeclaration. - The host or user supplies
GITHUB_TOKENand `D ...[truncated 1519 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove
GITHUB_TOKENandDASHBOARD_SECRETfromcredentials,metadata.openclaw.requires.env, andprimaryEnv. - Do not require any secret merely to install or read this non-executable guide.
- Request credentials only when a user explicitly performs an optional deployment or private-content-delivery operation.
- For GitHub access, recommend a fine-grained, read-only token restricted to the single content repository and only the required content permissions.
- Keep the dashboard secret in the deployed server's secret manager or protected environment, not in the Skill-loading environment.
- Prevent secrets from appearing in command history, logs, generated configuration, or client-side output.
- Align the metadata name
WALLET_ADDRESSwith the documented configuration nameAGENT_WALLET_ADDRESSto avoid users provisioning unintended variables. - Clearly separate “guide requirements” from “optional deployment requirements” in both metadata and documentation.
- If future versions add executable files, ensure those files receive only operation-specific credentials at invocation time and add automated checks for unexpected environment-variable access or outbound transmission.
- Remove
