T09 · Insecure Skill Coding Practices
- Location
index.js:96- Finding
Sensitive QR Content Exposed Through URL Query Parameters
- Content
View full analysis
Vulnerability Details
File Location:
index.js, line 96
Vulnerability Type: Sensitive information exposure through URL query parameters
Risk Level: MediumVulnerable Code
js const qrUrl = `${siteOrigin()}/qr-generator?text=${encodeURIComponent(content)}&size=${size}&error=${errorLevel}`;The documentation explicitly presents credentials as expected QR content:
text /lynqn qr "Wi-Fi: MyNetwork, Password: 12345" --size 400 --error HTechnical Analysis
The skill inserts arbitrary user-provided QR content into the
textquery parameter of an externally hosted URL.encodeURIComponent()makes the value syntactically safe for a URL, but it does not encrypt, redact, or otherwise protect the content.When the returned URL is opened, its complete query string may be retained by browser history, the LYNQN server's access logs, reverse proxies, monitoring infrastructure, analytics systems, and other components that record URLs. It may also be disclosed through referrer information, depending on browser and server policies.
This is security-relevant because the documented use cases explicitly encourage users to process Wi-Fi passwords. The same command could be used with access tokens, personal data, private URLs, or other secrets.
Attack Path
- A user invokes
/lynqn qrwith sensitive content, such as a Wi-Fi password or access token. - The skill embeds the complete content into the
textquery parameter of a LYNQN URL. - The skill returns that URL in the agent's reply.
- The user opens the URL to generate or download the QR code.
- The browser sends the complete query string to the external LYNQN service.
- The sensitive value may be retained in browser history or recorded by servers, proxies, monitoring tools, or analytics systems.
- An attacker or unauthorized operator with access to any such records may recover the original secret.
Impact Assessment
Successful exploitation does not grant local code e ...[truncated 409 chars]
- A user invokes
- Remediation
View remediation
Remediation Suggestions
- Generate QR codes locally so the QR payload never needs to be disclosed to an external service.
- If server-side generation is required, transmit the content in the body of an HTTPS
POSTrequest rather than in a URL query parameter. - Return an opaque, short-lived identifier instead of a URL containing the original content.
- Configure the remote service and intermediaries to avoid logging request bodies containing QR payloads, and apply strict retention and access controls.
- Add an explicit warning that users must not submit passwords, tokens, private keys, or other secrets unless a confidential processing design is implemented.
- Remove credential-bearing QR examples from
README.mdand replace them with non-sensitive sample content. - Apply an appropriate restrictive
Referrer-Policyon the QR page as defense in depth, while recognizing that this does not prevent browser-history or server-log exposure.
