T09 · Insecure Skill Coding Practices
- Location
SKILL.md:55- Finding
Full Medication Configuration Can Be Exposed Through Chat
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:55
Vulnerability Type: Sensitive information exposure through an unrestricted configuration-display command
Risk Level: MediumVulnerable Code Snippet
markdown | `show config` | Display the current pills.md content. |The sensitivity and scope of the exposed configuration are established in
SKILL.md:138-139:markdown | Config | `~/.openclaw/workspace/pills.md` | All profiles, pills, schedules, counts | | Log | `~/.openclaw/workspace/pill-log.md` | Adherence history, dates taken/missed |The same command is also documented in
README.md:88:markdown | `show config` | Display your current pills.md file. |Technical Analysis
The
show configcommand directs the agent to return the complete contents ofpills.md. According to the documented data model, this file can contain profile names, medication names, dose schedules, remaining pill counts, refill thresholds, and information about multiple household members.The skill operates through configurable messaging channels, including potentially shared GroupMe, Discord, or Telegram conversations. No documented control requires this command to run in a private channel, verifies that the requester is the configuration owner, limits the response to the requester's profile, requests confirmation, or redacts sensitive fields.
Consequently, raw health-related configuration data may be disclosed to unintended channel participants. This is an insecure handling and presentation practice for sensitive local data.
Attack Path
- A user configures the skill with one or more profiles and medication schedules.
- The skill stores those details in
~/.openclaw/workspace/pills.md. - The bot is used in a shared or otherwise insufficiently private messaging channel.
- An unauthorized or unintended participant invokes
show config, or the legitimate owner invokes it without realizing that the response will be visible to o ...[truncated 961 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove raw configuration display functionality from chat-facing commands, or replace it with a safe, structured summary.
- Require authenticated owner authorization before returning any configuration information.
- Refuse to display sensitive configuration in group channels; require a verified private conversation.
- Restrict output to the requester's own profile instead of returning all household profiles.
- Redact medication names, schedules, counts, and family-member identifiers unless each field is explicitly requested and disclosure is confirmed.
- Add a confirmation prompt that clearly identifies the destination channel and categories of data that will be exposed.
- Apply least-privilege access controls so family profiles can be viewed only by specifically authorized users.
- Avoid returning raw file contents. Parse the file and emit only allowlisted fields.
- Add security tests covering unauthorized users, shared channels, cross-profile access, redaction, and accidental group-chat disclosure.
- Update
README.mdandSKILL.mdso their privacy claims clearly explain that chat output leaves local storage and may be retained by the messaging provider.
