other
- Location
SKILL.md:36- Finding
Unredacted Conversation Upload with Indefinite Third-Party Retention
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 36-39; retention behavior documented at lines 48-49
Vulnerability Type: Sensitive conversation disclosure
Risk Level: Highpython mem.ingest(user_id, messages=[ {"role": "user", "content": user_message}, {"role": "assistant", "content": reply}, ])The associated retention policy is:
text 3. `mem.ingest()` saves the full conversation exchange asynchronously 4. Memory persists indefinitely — no TTL, no purgeTechnical Analysis
The Skill instructs the agent to transmit complete user and assistant messages to the external getmem.ai service after every turn. It does not prescribe data classification, secret detection, redaction, user consent, selective ingestion, retention limits, or deletion controls.
Persistent memory is necessary for the declared functionality, but uploading every complete exchange and retaining it indefinitely exceeds the minimum data access and retention required. Conversations can contain credentials, personal information, proprietary source code, internal system details, or other confidential material. Asynchronous ingestion may also make it difficult for users to prevent or reverse disclosure after a sensitive message has been processed.
Attack Path
- A user submits a message containing confidential information, credentials, personal data, or proprietary content.
- The agent processes the message and generates a response.
- Following the Skill instructions, the agent passes both complete messages to
mem.ingest(). - The external service receives and retains the exchange indefinitely.
- An account compromise, service breach, unauthorized operator access, or unintended retrieval exposes the retained information.
Impact Assessment
Exploitation does not directly grant local operating-system privileges. However, it can expose all sensitive information present in ingested conversat ...[truncated 245 chars]
- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed user opt-in before transmitting conversation data.
- Default to local or session-scoped storage where persistent remote storage is unnecessary.
- Ingest only explicitly selected facts rather than complete conversation turns.
- Apply secret detection and redaction for API keys, passwords, tokens, personal data, and proprietary content.
- Define configurable retention periods and provide verified deletion, export, and account-purge mechanisms.
- Permit users and administrators to disable ingestion for sensitive sessions or message classes.
- Document the receiving service, processing purpose, storage region, retention policy, subprocessors, and access controls.
- Encrypt data in transit and at rest, isolate data by tenant and user identity, and maintain access audit logs.
