T09 · Insecure Skill Coding Practices
- Location
SKILL.md:15- Finding
Bearer Token Transmitted over Plaintext HTTP
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:15,SKILL.md:28-31,references/workflow.md:9-11
Vulnerability Type: Sensitive credential transmission over an unencrypted channel
Risk Level: HighVulnerable Code
SKILL.md:15:text - `RAGTOP_API_URL`: API Base URL (optional, default `http://10.71.10.71:9380`)SKILL.md:28-31:bash curl -L -X POST "${RAGTOP_API_URL}/api/v1/ragtop/tool/list_kb" \ -H "Authorization: Bearer ${RAGTOP_API_TOKEN}" \ -H "Content-Type: application/json"Technical Analysis
The default RAGTOP API endpoint uses plaintext HTTP while requests transmit
RAGTOP_API_TOKENin theAuthorizationheader. HTTP provides neither transport confidentiality nor server authentication. An attacker able to observe or manipulate network traffic can recover the bearer credential, inspect retrieved knowledge-base records, or alter API responses.Because this is a bearer token, possession may be sufficient to impersonate the legitimate tenant without obtaining any additional secret. The use of an internal IP address does not provide transport security; compromised hosts, malicious network peers, unsafe proxies, and incorrectly segmented internal networks remain viable interception points.
Attack Path
- A user invokes the Skill without overriding the default
RAGTOP_API_URL. - The Skill sends an HTTP request to
10.71.10.71:9380. - The request includes
Authorization: Bearer ${RAGTOP_API_TOKEN}in plaintext at the transport layer. - An attacker with access to the relevant network path captures the request or performs a machine-in-the-middle attack.
- The attacker extracts and reuses the token against RAGTOP endpoints.
- Subject to the token's assigned permissions, the attacker enumerates knowledge bases, lists documents, retrieves tenant data, or submits manipulated responses during interception.
Impact Assessment
Successful exploitatio ...[truncated 388 chars]
- A user invokes the Skill without overriding the default
- Remediation
View remediation
Remediation Suggestions
- Change the default endpoint to an HTTPS URL with a valid certificate.
- Reject
http://API URLs by default rather than silently transmitting credentials over them. - If plaintext HTTP is required for isolated development, require an explicit insecure-development flag and prevent use with production tokens.
- Validate server certificates and hostnames; do not disable TLS verification in clients or examples.
- Apply narrow scopes, tenant restrictions, short expiration periods, and regular rotation to API tokens.
- Rotate any token that may already have been transmitted using the documented HTTP default.
- Consider network-level restrictions and certificate pinning where the deployment model supports them.
