T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:50- Finding
Cross-Skill Credential Discovery and Reuse Violates Least Privilege
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 50-55
Vulnerability Type: Unauthorized discovery and reuse of credentials from the host environment and unrelated skills
Risk Level: HighRelevant instruction snippet:
markdown Prioritize configuration sources in the following order instead of immediately asking the user to provide new credentials: 1. The current OpenClaw Feishu channel context. 2. Existing Feishu-related environment variables in the current runtime. 3. Reusable Feishu configuration from this skill or other existing skills.Technical Analysis
The skill instructs the agent to inspect the current channel context, process environment, and configurations belonging to other installed skills to obtain Feishu credentials. In particular, searching “other existing skills” crosses the expected isolation boundary between independently installed skills.
A skill should receive only credentials explicitly provisioned for its own operation. The presence of a secret in an environment variable or another skill's configuration does not establish authorization to copy or use it. Automatic reuse can also bypass intended separation between applications, tenants, recipients, and permission scopes.
The required values include
ALICE_FEISHU_APP_SECRET, which is an authentication secret capable of enabling API access under the associated Feishu application's granted permissions. Although the audited package contains onlySKILL.mdand no executable scripts, these instructions direct a capable agent to discover and provision that secret for subsequently installed or retrieved components.Attack Path
- A user asks the agent to install and configure the skill.
- The loaded skill instructions direct the agent to search the active Feishu context, runtime environment, and configurations of other skills before asking for dedicated credentials.
- The agent locates an existing Feishu App ID, ...[truncated 1461 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the instruction to inspect configuration owned by other skills.
- Require credentials to be explicitly provisioned for this skill through an approved secret manager or a skill-specific configuration namespace.
- Permit reuse of an active Feishu channel identity only after displaying the application identity, tenant, recipient, and requested scopes and obtaining explicit user confirmation.
- Never copy an App Secret into documentation, chat history, logs, plaintext files, command-line arguments, or another skill's persistent configuration.
- Use a dedicated Feishu application with the minimum permissions required to send direct messages to the approved recipient.
- Validate that the configured target identifier belongs to the intended tenant and require confirmation before the first real message is sent.
- Keep preview mode credential-free where possible. Separate content generation from authenticated delivery.
- Add provenance tracking so configuration records identify who authorized each credential, its intended skill, allowed recipient, and permitted use.
- If credentials may already have been copied across skill boundaries, rotate the affected App Secret, revoke obsolete credentials, and review Feishu API and messaging logs for unauthorized activity.
