other
- Location
SKILL.md:28- Finding
Unprotected Transmission of Potentially Sensitive Agent Memory to an External Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 28–34 and 43–53
Vulnerability Type: External transmission and storage of potentially sensitive agent memory
Risk Level: MediumThe skill presents a cloud memory service and instructs users or agents to submit project information to
https://api.openviking.pro.python import requests # 저장 requests.post("https://api.openviking.pro/v1/memory/save", json={ "uri": "memories/project", "content": "프로젝트 정보..." }) # 검색 (토큰 96% 절약) response = requests.post("https://api.openviking.pro/v1/memory/search", json={ "query": "프로젝트", "level": 0 # 요약만 })Technical Analysis
The
/v1/memory/saveexample sends agent or project context to a third-party cloud endpoint for persistent storage. In realistic use, the placeholdercontentvalue may be replaced with conversation history, source code, internal project information, personal data, access tokens, or other confidential context.The skill does not require explicit user approval before an upload and provides no guidance for local data classification, secret detection, redaction, data minimization, retention, deletion, tenant isolation, or access control. It also advertises shared cloud memory, increasing the possible disclosure scope if stored records are accessible to multiple users or agents.
This is not evidence that the external service is malicious or that a breach has occurred. The risk arises from directing sensitive agent state across the local trust boundary without documenting adequate safeguards.
Attack Path
- An agent or user loads the skill and follows its cloud-memory workflow.
- Real project or conversation context is substituted for the example
"프로젝트 정보..."content. - The client submits that content to
https://api.openviking.pro/v1/memory/save. - The external provider stores the submitted memory outside the local environment.
- Stored conten ...[truncated 996 chars]
- Remediation
View remediation
Remediation Suggestions
- Require informed, explicit user approval before transmitting any conversation, project, or memory content to the external service.
- Clearly display the destination, data categories, purpose, retention period, sharing scope, and deletion process before upload.
- Apply local secret detection and redaction for API keys, passwords, tokens, private keys, personal information, and other confidential values.
- Use data minimization: send only the fields and excerpts required for the requested operation rather than complete histories or project contexts.
- Provide allowlist and denylist controls for memory types and data sources.
- Document authentication, authorization, tenant isolation, encryption, retention, deletion, audit logging, and team-sharing controls.
- Store API credentials in a protected secret manager or environment variable rather than in skill text, source code, or uploaded memory.
- Offer a configurable endpoint or local-only storage mode for environments that cannot permit third-party data transfer.
- Add warnings that credentials, regulated data, proprietary source code, and personal information must not be uploaded without authorization.
- Provide mechanisms to inspect, export, revoke sharing for, and permanently delete previously uploaded records.
