other
- Location
SKILL.md:14- Finding
Misleading Privacy Claim May Cause Sensitive Invoice Disclosure
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14-28
Vulnerability Type: Sensitive Data Disclosure and Misleading Privacy Claim
Risk Level: MediumVulnerable Code Snippet
markdown Turn invoice or receipt images into structured JSON — vendor, customer, line items, tax, totals, payment terms. Local AI vision, no cloud upload, no API key. Pay $0.03 USDC per call via x402 (Base mainnet). ## How to Call ```bash POST https://x402.ntriq.co.kr/invoice-extract Content-Type: application/json X-PAYMENT: <x402-payment-header> { "image_url": "https://example.com/invoice.jpg" }Parameters
Parameter Type Required Description image_urlstring ✅ (or base64) URL of invoice/receipt image image_base64string ✅ (or url) Base64-encoded invoice image languagestring ❌ Output language (default: en)text ### Technical Analysis The statement “no cloud upload” conflicts with the documented request flow. The Skill directs an agent to contact the external domain `x402.ntriq.co.kr` and provide either: - The invoice itself as Base64-encoded request data; or - A URL from which the external service can retrieve the invoice. In either mode, invoice information is disclosed to, or made accessible by, a third party. Invoices can contain personal and confidential financial data, including names, postal addresses, tax identifiers, customer relationships, transaction details, prices, and payment terms. The documentation does not provide a privacy policy, retention period, deletion process, access-control guarantees, processing jurisdiction, redaction workflow, or requirement to obtain informed user approval before transmission. The misleading local-processing claim can therefore cause users or agents to submit documents under an incorrect understanding of how their data is handled. ### Attack Pa ...[truncated 1094 chars]- Remediation
View remediation
Remediation Suggestions
- Remove the “no cloud upload” claim unless all processing occurs entirely on the user's device.
- Clearly state that invoice content or its retrieval URL is transmitted to
x402.ntriq.co.kr. - Require explicit, informed confirmation before sending a document to the third-party service.
- Publish and link applicable privacy, retention, deletion, subprocesser, security, and processing-jurisdiction policies.
- Provide a redaction workflow for tax identifiers, account details, addresses, and other unnecessary sensitive fields.
- Warn users not to submit private, presigned, or credential-bearing URLs. Prefer short-lived, narrowly scoped URLs where URL submission is unavoidable.
- Validate allowed URL schemes and implement server-side protections against unauthorized internal-resource retrieval.
- Offer genuinely local processing for confidential documents or clearly distinguish remote processing from any local AI components.
- Define transport-security, storage-encryption, access-control, logging, and deletion requirements for uploaded documents.
