T09 · Insecure Skill Coding Practices
- Location
SKILL.md:142- Finding
Bearer API Credentials Transmitted over Plaintext HTTP
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:142-143
Additional Locations:SKILL.md:16,SKILL.md:182-183,SKILL.md:269-270,SKILL.md:307-308,SKILL.md:360-361,SKILL.md:400-401
Vulnerability Type: Cleartext transmission of sensitive credentials
Risk Level: HighVulnerable Code
bash curl "http://ipaynapi.gpuart.cn/user/me" \ -H "Authorization: Bearer YOUR_API_KEY"The same plaintext HTTP pattern is documented for
/user/my-keys:bash curl "http://ipaynapi.gpuart.cn/user/my-keys" \ -H "Authorization: Bearer YOUR_API_KEY"Technical Analysis
The Skill instructs users to transmit a bearer API key to
ipaynapi.gpuart.cnover unencrypted HTTP. Bearer credentials grant access based solely on possession, so transport-layer confidentiality and integrity are mandatory.HTTP provides neither property. Network intermediaries can observe the
Authorizationheader or modify the server response. The endpoints are especially sensitive because/user/meand/user/my-keysreturn account information, wallet metadata, transaction details, and active API keys.This behavior is not required for the declared account-management functionality. The same requests should be made exclusively over authenticated HTTPS.
Attack Path
- A user follows the Skill documentation and calls an account endpoint using
http://ipaynapi.gpuart.cn. - The request traverses an untrusted network, proxy, gateway, Wi-Fi access point, or other intermediary.
- An attacker captures the plaintext
Authorization: Bearer ...header. - The attacker replays the stolen bearer credential against the user-management service.
- Subject to the credential's server-side privileges, the attacker retrieves account details, wallet metadata, usage information, transaction history, or API-key records.
- A man-in-the-middle attacker may also modify plaintext responses presented to the user.
...[truncated 459 chars]
- A user follows the Skill documentation and calls an account endpoint using
- Remediation
View remediation
Remediation Suggestions
- Replace every
http://ipaynapi.gpuart.cnURL with an authenticatedhttps://endpoint. - Configure the server to reject plaintext HTTP rather than silently serving authenticated endpoints over it.
- Redirecting HTTP to HTTPS is not sufficient for requests already carrying credentials; clients must originate authenticated requests over HTTPS.
- Enable HSTS with an appropriate policy after confirming complete HTTPS support.
- Validate certificates and hostnames using standard TLS verification. Do not add certificate-verification bypasses.
- Rotate any API key that may previously have been transmitted over plaintext HTTP.
- Minimize endpoint responses so that one API key cannot unnecessarily retrieve other complete API-key values.
- Consider short-lived, scoped access tokens instead of long-lived bearer API keys for account-management operations.
- Replace every
