T09 · Insecure Skill Coding Practices
- Location
SKILL.md:27- Finding
Sensitive Personal Identifiers Embedded in HTTPS URL Paths
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 27-32; supporting usage example at line 37
Vulnerability Type: Sensitive data exposure through URL paths
Risk Level: MediumVulnerable Code
markdown | `GET https://api.gocreativeai.com/v1/enrich/company/{domain}` | B2B company enrichment from a domain (firmographics) | ~$0.05 | | `GET https://api.gocreativeai.com/v1/enrich/email/{name-and-domain}` | Find a person's likely **work email** from name + company domain | ~$0.02 | | `GET https://api.gocreativeai.com/v1/bundle/email-360/{email}` | **Email 360**: deliverability validation + provider/domain enrichment | ~$0.15 | | `GET https://api.gocreativeai.com/v1/enrich/domain/{domain}` | Domain intel: DNS + WHOIS + TLS, fused | ~$0.05 | | `GET https://api.gocreativeai.com/v1/enrich/linkedin/{profile}` | LinkedIn profile enrichment | ~$0.05 | | `GET https://api.gocreativeai.com/v1/bundle/company-360/{domain}` | **Company 360**: full domain intelligence bundle | ~$0.15 |The documented example further demonstrates direct placement of an email address in a URL path:
markdown - Find + verify an email: `GET /v1/enrich/email/jane-doe-acme.com` → then `GET /v1/bundle/email-360/jane@acme.com`.Technical Analysis
The Skill instructs agents to insert names, email addresses, LinkedIn profile identifiers, and company domains directly into HTTPS URL paths. TLS protects the request while it is in transit, but it does not prevent full URLs from being recorded by the client, API gateway, reverse proxy, web server, monitoring platform, tracing system, or access logs.
Email addresses and profile identifiers are personal data. Using them as path parameters increases their exposure and retention across infrastructure components that routinely log request targets. URL encoding does not provide confidentiality; it only makes values syntactically safe for transport.
Attack Path
- An agent recei ...[truncated 1118 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace endpoints that accept personal identifiers in URL paths with authenticated HTTPS
POSTendpoints. - Put email addresses, names, and profile identifiers in a structured JSON request body.
- Configure clients, gateways, proxies, servers, observability tools, and error-reporting systems to redact sensitive request fields.
- Define and publish data-retention, deletion, and access-control policies for submitted identifiers.
- Require agents to obtain appropriate authorization before transmitting third-party personal data.
- Minimize submitted information and avoid sending unnecessary profile or contact details.
- If compatibility requires retaining
GETendpoints, use short-lived opaque request tokens rather than raw personal identifiers.
- Replace endpoints that accept personal identifiers in URL paths with authenticated HTTPS
