T09 · Insecure Skill Coding Practices
- Location
SKILL.md:104- Finding
API Key and Administrative Data Transmitted over Plaintext HTTP
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:104-109; related examples also appear inREADME.md:39andREADME.md:47-52
Vulnerability Type: Plaintext transmission of sensitive credentials and server data
Risk Level: HighVulnerable code snippet (
SKILL.md:104-109):yaml default_profile: lab profiles: lab: host: http://192.168.1.10:7777 apiKey: YOUR_API_KEY output: jsonRelated command example (
README.md:39):bash ucli --host http://192.168.1.10:7777 --api-key YOUR_API_KEY system infoRelated configuration example (
README.md:47-52):yaml default_profile: lab profiles: lab: host: http://192.168.1.10:7777 apiKey: YOUR_API_KEY output: table timeout: 30Technical Analysis
The documented configuration sends an API key to an Unraid GraphQL endpoint using unencrypted HTTP. The network transmission is necessary for the Skill's declared remote-management functionality, but plaintext transport is not the minimum safe mechanism for carrying administrative credentials.
An attacker able to observe or manipulate traffic on the network path may recover the API key, inspect sensitive GraphQL responses, or modify requests and responses. The affected data can include server health information, disk and share details, network configuration, container and VM metadata, logs, notifications, and diagnostic results.
The command-line example also places the API key in a process argument. Depending on the operating system and shell configuration, this may expose the credential through process listings, command history, diagnostic collection, or terminal logs.
Attack Path
- A user or agent follows the documented example and connects to the Unraid API through
http://. - An attacker gains visibility into the network path, such as through a compromised local device, malicious access point, switched-network at ...[truncated 1176 chars]
- A user or agent follows the documented example and connects to the Unraid API through
- Remediation
View remediation
Remediation Suggestions
- Replace all plaintext HTTP examples with HTTPS URLs and require TLS for authenticated API requests.
- Reject
http://endpoints by default. If plaintext transport is needed for isolated development, require an explicit insecure override accompanied by a prominent warning. - Validate server certificates and hostnames. Do not recommend disabling certificate verification.
- For private or self-signed deployments, document how to configure a trusted local certificate authority rather than bypassing validation.
- Recommend dedicated, least-privilege API keys limited to the operations required by each automation task.
- Avoid passing API keys through
--api-keywhere possible. Prefer a protected environment variable, restricted credential file, or operating-system secret store. - Ensure configuration files containing credentials are created with owner-only permissions and are excluded from source control, logs, and diagnostics.
- Redact authentication material from verbose output, errors, telemetry, and diagnostic commands.
- Provide key rotation and revocation guidance in case a credential has previously been sent over plaintext HTTP.
