T09 · Insecure Skill Coding Practices
- Location
SKILL.md:211- Finding
External transmission of potentially confidential product images lacks a mandatory consent and data-handling gate
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 211–235
Vulnerability Type: Sensitive information disclosure to a third-party service
Risk Level: MediumVulnerable Code Snippet
text Use the official Patsnap Patent Research MCP server for live FTO execution. Official page: https://open.patsnap.com/marketplace/mcp-servers/patsnap-ip-searching Configuration key: `patsnap_patent_research`. Transport: `streamableHttp`. Current Connect-panel pattern verified on 2026-08-07: `https://open.patsnap.com/marketplace/mcp-servers/patsnap-ip-searching` Always copy the current URL from the official Connect panel. Never place a real API key in the report, skill, source control, or logs. Use `fto_review` for invention-patent FTO screening. Use country, application-date, legal-status, and assignee filters as appropriate. Use `search.mode: lite` for a clearly labeled preliminary screen. Use `search.mode: pro` when the task and available access justify deeper analysis. Use `design_fto` for design-risk screening from one product or design image. Remember that only the first `input.images` item is used by that tool. Select the most representative view for the tool call. Run separate calls for materially different views when necessary.Technical Analysis
The Skill instructs the Agent to use an external PatSnap MCP service for live freedom-to-operate analysis and to submit a representative product or design image to
design_fto. Automotive drawings and product images may reveal confidential geometry, unreleased styling, dimensions, program details, or trade secrets.This network operation is relevant to the declared patent and design-right screening functionality, and the destination is represented as PatSnap's official service. The instructions also prohibit placing API keys in reports, source control, or logs. Therefore, the reviewed content does not demonstrate credential theft or intentional malicious exfiltration.
Howeve ...[truncated 2766 chars]
- Remediation
View remediation
Remediation Suggestions
-
Add a mandatory pre-transfer confirmation that identifies:
- The specific external service.
- The files or images to be transferred.
- The purpose of the transfer.
- Whether multiple views will be submitted.
-
Require explicit user consent before the first external submission. Consent to perform an analysis should not automatically be treated as consent to disclose confidential artifacts to a third party.
-
Add a confidentiality gate requiring the Agent to determine whether submitted material is:
- Public.
- Internal.
- Confidential.
- Subject to an NDA.
- Export-controlled or otherwise restricted.
-
Require confirmation that third-party processing is authorized under applicable organizational policy and contractual obligations.
-
Enforce data minimization:
- Crop images to the feature needed for comparison.
- Redact labels, dimensions, program names, and unrelated geometry.
- Strip EXIF and other metadata.
- Avoid transmitting additional views unless necessary and separately approved.
- Prefer reduced-resolution copies when sufficient.
-
Require disclosure or verification of relevant service policies, including retention, deletion, model-training use, data residency, access controls, and subprocessors.
-
Provide a safe fallback for restricted material, such as a documented search strategy, locally prepared feature description, or user-executed search plan that does not upload the original image.
-
Record only a minimal audit entry indicating authorization and the submitted artifact category. Do not log image contents, credentials, or raw confidential service responses.
-
Preserve the existing prohibition on embedding API keys in reports, source control, and logs.
-
