T09 · Insecure Skill Coding Practices
- Location
SKILL.md:16- Finding
Plaintext HTTP Used for Primary Weather Service
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16-38
Vulnerability Type: Plaintext external-service communication
Risk Level: LowComplete vulnerable code snippets:
bash curl -s "wttr.in/London?format=3"bash curl -s "wttr.in/London?format=%l:+%c+%t+%h+%w"bash curl -s "wttr.in/London?T"bash curl -s "wttr.in/Berlin.png" -o /tmp/weather.pngTechnical Analysis
The documented
wttr.inURLs omit an explicithttps://scheme.curlconsequently treats these URLs as HTTP, causing at least the initial request to be transmitted without TLS protection. Even if the service redirects clients to HTTPS, the original plaintext request remains susceptible to interception or modification, and these commands do not use--locationto follow redirects.An attacker positioned on the network path, such as an operator of a malicious Wi-Fi access point or a compromised gateway, could observe the requested location, modify a plaintext response, or replace a redirect. Weather output is data rather than executable code, so this issue does not by itself provide code execution or elevated system privileges.
Attack Path
- A user or agent follows the Skill instructions and executes one of the documented
curlcommands. curlsends a plaintext HTTP request containing the requested city, airport code, or other location.- A network-positioned attacker intercepts the request.
- The attacker learns the requested location or modifies the returned weather content.
- The user or agent consumes the attacker-controlled response as if it originated from the legitimate weather service.
Impact Assessment
The issue can disclose weather-query locations and compromise the integrity of returned weather data. An attacker can potentially provide false forecast information within the affected request. The finding does not grant local privileges, persistent access, ...[truncated 81 chars]
- A user or agent follows the Skill instructions and executes one of the documented
- Remediation
View remediation
Remediation Suggestions
Replace every scheme-less
wttr.inURL with an explicit HTTPS URL:bash curl --fail --show-error --silent "https://wttr.in/London?format=3" curl --fail --show-error --silent "https://wttr.in/London?format=%l:+%c+%t+%h+%w" curl --fail --show-error --silent "https://wttr.in/London?T" curl --fail --show-error --silent "https://wttr.in/Berlin.png" -o /tmp/weather.pngIf redirects are expected, add
--locationwhile retaining the explicit HTTPS scheme. Do not disable TLS certificate validation. Where location values are dynamically supplied, URL-encode them before constructing the request.
