other
Warning
- Location
- SKILL.md:21
- Finding
- Unspecified Remote Model Fallback May Disclose Sensitive Task Data## Vulnerability Details **File Location**: `SKILL.md:21-22`, `SKILL.md:45-47`, and `SKILL.md:88-91` **Vulnerability Type**: Unspecified remote data disclosure risk **Risk Level**: Medium **Relevant Skill Text**: ```markdown ### Connectivity Awareness - **Internet Detection**: Monitor internet connectivity status - **Smart Fallback**: Switch to remote models when local models unavailable and internet is present - **Offline Mode**: Maintain full functionality without internet ``` ```markdown ### When Internet is Available - Use local models primarily - Fallback to remote models if local models unavailable - Maintain optimal performance ``` ```markdown ## Security Considerations - All operations performed locally - No external dependencies required - Secure model management - Privacy-preserving by default ``` ### Technical Analysis The Skill authorizes automatic fallback to an unspecified remote model when local models are unavailable. Remote inference normally requires transmitting at least the user prompt and associated task context to an external service. The document does not identify the provider, endpoint, authentication mechanism, transmitted fields, retention policy, transport-security requirements, or a required user-consent step. This behavior conflicts with the assertions that all operations are local and privacy-preserving by default. The issue is contained in the Skill instructions; the audited project contains no executable implementation with which to verify whether consent, redaction, endpoint allowlisting, or other safeguards exist. ### Attack Path 1. The primary and alternative local Ollama models become unavailable, whether because of an ordinary failure, resource exhaustion, or deliberate disruption. 2. The Skill detects that internet connectivity is available. 3. Its fallback instructions select an unspecified remote model. 4. The current prompt and potentially related con ...[truncated 676 chars]
- Remediation
- ## Remediation Suggestions 1. Disable remote fallback by default and require explicit, informed user approval before transmitting task data externally. 2. Identify and allowlist approved providers, HTTPS endpoints, model identifiers, and authentication mechanisms. 3. Clearly document which request fields and context are transmitted, along with provider retention and privacy policies. 4. Minimize submitted context and redact credentials, tokens, personal information, proprietary code, and other secrets before transmission. 5. Provide a strict local-only configuration that cannot silently activate a remote provider. 6. Log fallback decisions and display the selected provider without recording sensitive prompt content. 7. Replace the claim that all operations are local, or constrain the design so that the claim is accurate.
