other
- Location
SKILL.md:15- Finding
Unnecessary External Transmission of Sensitive Financial Data
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15-32
Vulnerability Type: Excessive external transmission of financial data
Risk Level: MediumThe Skill requires property and investment-related financial data to be submitted to Vestafolio's external API, even though
SKILL.mddocuments the formulas necessary to perform the calculation locally.Vulnerable Code Snippet:
text 1. Reuse answers already supplied. Ask the missing questions below before giving a numerical result or a personalized recommendation. Example values and schema defaults are not the user's answers. 2. Before sending inputs, explain that this calculation uses Vestafolio's external API at `https://www.vestafolio.com`, summarize the fields and values to be sent, and obtain the user's agreement. Existing explicit approval for this destination and data scope is sufficient; do not ask again for calls it already covers. Installing or selecting the skill alone is not approval to transmit personal data. If the user declines, do not POST; offer the simulator link for manual use without prefilled inputs. 3. Once inputs and approval are known, actually call a tool: fetch the schema, then POST only the relevant simulator fields to the endpoint below. Omit unused optional data, names, addresses, account identifiers, credentials, files, and conversation history. No authentication is needed. Use an available HTTP tool, a terminal with curl, or Python code execution (`execute_code` in OpenWebUI). Python can use `urllib.request`; in browser-based Pyodide use `await pyfetch(...)` from `pyodide.http`. A Python environment does not need a shell to call the API.The required request is demonstrated later in the file:
bash curl --fail-with-body --silent --show-error --max-time 30 -X POST https://www.vestafolio.com/api/tools/v1/rentabilite-locative \ -H 'Content-Type: appli ...[truncated 3593 chars]- Remediation
View remediation
Remediation Suggestions
- Implement the documented formulas locally and make local calculation the default behavior.
- Treat the external API as an optional verification mechanism rather than a mandatory dependency.
- Before optional API use, continue to identify the destination, enumerate the exact fields and values, and obtain explicit, scope-specific consent.
- Preserve the existing data-minimization rules that prohibit sending names, addresses, credentials, account identifiers, files, unused fields, and conversation history.
- Publish or link to the service's privacy policy and clearly disclose retention periods, subprocessors, deletion options, and whether submitted data is used for analytics or model training.
- Validate all values locally against documented bounds before transmission and send only the minimum fields required by the current schema.
- Provide a local fallback when network access is unavailable or consent is declined, instead of refusing to calculate despite having the necessary formulas.
- If API parity is operationally important, add tests comparing local calculations with anonymized API test vectors rather than sending each user's real financial inputs.
