T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:63- Finding
Overbroad Access to a Credential-Bearing Environment File
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:63-66; mirrored inTEMPLATE.md:96-102
Vulnerability Type: Sensitive configuration access exceeding least privilege
Risk Level: MediumVulnerable snippet from
SKILL.md:markdown ### Jenny Activation — `TOOL_FAILURE` - Check config: `~/.openclaw/workspace-jenny/.env` must contain `supabaseUrl` - If missing → classify `human_required` (Ray must fix config) - If config ok → RUN: `node workspace-jenny/scripts/jenny/send-activation-batch.mjs batch`Mirrored snippet from
TEMPLATE.md:markdown ### 8. Jenny Activation **Expected:** activation execution receipt + acceptance receipt **Check:** `workspace-jenny/.env` for `supabaseUrl` **Recovery action:** - If config missing → `human_required`, write blocker receipt - If config ok → RUN activation batch script, capture logTechnical Analysis
The Skill directs the Agent to inspect a complete
.envfile located in another workspace merely to determine whether one configuration property,supabaseUrl, exists. Environment files commonly contain API keys, service-role credentials, database secrets, and other values unrelated to this check.The configuration check is relevant to the declared activation-recovery function, but granting the Agent visibility into the whole file is broader than necessary. The documentation also lacks an explicit prohibition against displaying, recording, or copying the file contents into model context, command output, recovery tickets, receipts, or runner logs.
No instruction was found that deliberately transmits these credentials externally. The risk arises from unnecessary secret exposure and subsequent accidental disclosure rather than demonstrated exfiltration.
Attack Path
- The Jenny activation lane enters a
TOOL_FAILUREstate. - The Agent follows the documented recovery procedure and opens
workspace-jenny/.env. - The file ex ...[truncated 795 chars]
- The Jenny activation lane enters a
- Remediation
View remediation
Remediation Suggestions
- Replace direct
.envinspection with a trusted local validation command that returns only a boolean or redacted status. - Parse only the required key without printing its value or surrounding file contents.
- Run the validation in the Jenny workspace under an identity that has access only to the required configuration.
- Explicitly prohibit copying
.envcontents or credential values into Agent responses, tickets, receipts, and runner logs. - Ensure the
.envfile has restrictive filesystem permissions. - Prefer a non-secret configuration source for
supabaseUrlif the value is only a public service URL. - Keep the existing
human_requiredbehavior when configuration is absent or inaccessible.
- Replace direct
