- Location
- SKILL.md:88
- Finding
- User Prompts and Generated Outputs Are Disclosed to an External Service Without Privacy Controls<![CDATA[
## Vulnerability Details
**File Location**: `SKILL.md:88-100` and `SKILL.md:110-139`
**Vulnerability Type**: External transmission of potentially sensitive prompts and outputs
**Risk Level**: High
### Evidence
```bash
curl -X POST "https://effect-module-hub.base44.app/api/apps/697f17cef600c2033d97e2c9/functions/applyModule" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"moduleCid": "QmXXXXXXXX...",
"input": "Your input prompt here",
"parameters": {
"intensity": 7,
"coherenceFloor": 0.6
}
}'
```
```bash
curl -X POST "https://effect-module-hub.base44.app/api/apps/697f17cef600c2033d97e2c9/functions/submitReport" \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"moduleCid": "QmXXXXXXXX...",
"inputPrompt": "Your input prompt",
"outputText": "The generated output",
"agentHandle": "YourAgentName",
"modelName": "gpt-4",
"ratings": {
"coherence": 4,
"novelty": 5,
"usefulness": 4,
"safety": 5
},
"notes": "Optional observations about the trip"
}'
```
### Technical Analysis
The `applyModule` workflow sends the user's input prompt to `effect-module-hub.base44.app`. The trip-report workflow additionally sends both `inputPrompt` and `outputText`, along with agent and model metadata.
The skill does not require user consent, data classification, secret detection, redaction, minimization, or synthetic test data. It also does not describe the external service's retention, secondary use, deletion, access-control, or ownership policies. Consequently, an agent following these instructions could transmit sensitive conversation content beyond the local trust boundary.
TLS protects data in transit but does not prevent the receiving service from storing, inspecting, correlating, or redistributing submitted content.
### Attack Path
1. A user provides a prompt containing confidential, personal
...[truncated 982 chars]
- Remediation
- <![CDATA[
## Remediation Suggestions
- Require explicit user approval before each transmission of prompts or generated outputs.
- Clearly identify the destination service and the exact fields that will leave the local trust boundary.
- Default to synthetic, non-sensitive test prompts when evaluating modules.
- Implement local detection and redaction for credentials, API keys, personal data, proprietary identifiers, and confidential conversation content.
- Never transmit system prompts, developer instructions, tool results, hidden context, memory, or unrelated conversation history.
- Minimize trip reports to aggregate ratings unless the user separately approves sharing prompt and output text.
- Publish retention, deletion, ownership, training-use, and third-party-sharing policies.
- Provide a mechanism to delete previously submitted reports and associated metadata.
- Use scoped credentials and avoid including bearer tokens in logs, diagnostics, or reports.
- Add an enterprise-configurable deny policy that disables external submissions for sensitive workloads.
]]>