T09 · Insecure Skill Coding Practices
- Location
SKILL.md:47- Finding
Uncontrolled disclosure of user-provided text to third-party dictionary services
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47-75
Vulnerability Type: Unrestricted third-party data transmission
Risk Level: MediumVulnerable Code Snippet:
markdown ### 2. Web API fallback Ha helyi szótár nem elérhető, használj nyilvános API-t: - dict.sztaki.hu (magyar-angol, de van értelmező is) - Wiktionary API ## Gyors kezdés ```python # Példa szójelentés lekérdezésre def lookup_word(word): # 1. Helyi szótár keresés if word in local_dict: return local_dict[word] # 2. API fallback return fetch_from_api(word)Referenciák
- references/kozmondasok.md – 100+ magyar közmondás és szólás jelentéssel, példákkal
- references/magyar-szotar.json – fő szótár adatbázis
- references/arcanum-ertsz.md – Arcanum ÉrtSz. forrásdokumentáció
- references/morfológia.md – magyar nyelvtani szabályok, ragozások
Jegyzetek
- Mindig ellenőrizd a szótár forrás frissességét
- Nagy szövegeknél batch lookup-ot használj (token hatékony)
- Ha szó nem található, jelezd és ajánlj alternatívát
text ### Technical Analysis The Skill instructs the agent to use public web APIs whenever the local dictionary does not contain a requested word. The bundled local dictionary contains only four entries, so external fallback is likely during ordinary use. The instructions do not require the agent to: - Obtain explicit user consent before making a network request. - Determine whether the submitted text is confidential or contains personal information. - Restrict transmission to a single normalized dictionary word. - Redact names, identifiers, credentials, or other sensitive material. - Use a fixed allowlist of exact HTTPS API endpoints. - Explain third-party logging, retention, or privacy implications. - Remain in local-only mode when handling sensitive documents. The recommendation to perform batch lookups for large texts increases th ...[truncated 1811 chars]- Remediation
View remediation
Remediation Suggestions
- Default to local-only processing and treat network fallback as an optional capability.
- Obtain explicit user consent before sending any lookup data to a third party.
- Tell the user which service will receive the data and what exact terms will be transmitted.
- Send only individually normalized unknown words; never transmit complete sentences, paragraphs, documents, or unreviewed batches.
- Disable external lookup automatically when input may contain credentials, personal data, confidential business information, medical information, or legal material.
- Replace the generic
fetch_from_apibehavior with a fixed allowlist of exact HTTPS endpoints and enforce certificate validation, request timeouts, response-size limits, and safe response parsing. - Provide a local-only failure response when consent is absent, such as reporting that the term is not available in the bundled dictionary.
- Expand the bundled dictionary or use an approved offline linguistic database to reduce unnecessary external requests.
- Document applicable third-party privacy, retention, and logging policies.
- Remove or strictly constrain batch lookup behavior so that batches cannot reconstruct meaningful portions of the source text.
