T09 · Insecure Skill Coding Practices
- Location
SKILL.md:56- Finding
API Credential Transmitted over Unencrypted HTTP
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 56–58. The same insecure transport pattern is used by every documented API request. Vulnerability Type: Plaintext transmission of an API credential Risk Level: Highbash curl -s "http://47.102.196.1:8081/v1/sector_heat?top_n=10" \ -H "X-API-Key: $SANO_TOKEN" \ -H "Content-Type: application/json"Technical Analysis
The skill instructs the agent to transmit
SANO_TOKENin theX-API-Keyheader to an endpoint using plaintext HTTP. HTTP provides neither transport encryption nor server authentication. Consequently, any party capable of observing or modifying network traffic can read the API credential, inspect potentially sensitive queries and responses, or alter the returned healthcare and financial intelligence.This pattern affects all documented API operations, including company searches, financing events, clinical trials, market information, daily digests, and patent queries. Using a raw IP address also prevents meaningful hostname-based identity validation if TLS is later introduced without a properly validated certificate and domain.
Attack Path
- A user obtains a valid Sano API token and exports it as
SANO_TOKEN. - The agent follows
SKILL.mdand sends a request tohttp://47.102.196.1:8081. - An attacker with an on-path position, such as a malicious Wi-Fi operator, compromised router, network administrator, or upstream intermediary, captures the plaintext HTTP request.
- The attacker extracts the token from the
X-API-Keyheader. - The attacker reuses the token to issue unauthorized API requests within the permissions and usage limits assigned to the victim.
- Alternatively, the attacker modifies API responses in transit, causing the agent to present manipulated company, financing, clinical-trial, patent, or market information as legitimate data.
Impact Assessment
Successful exploitation exposes the victim's AP ...[truncated 557 chars]
- A user obtains a valid Sano API token and exports it as
- Remediation
View remediation
Remediation Suggestions
- Replace every
http://47.102.196.1:8081endpoint with an authenticatedhttps://endpoint hosted under a controlled domain. - Configure the server with a certificate issued for that domain by a trusted certificate authority.
- Preserve curl's default certificate and hostname verification. Do not introduce
--insecure,-k, or custom logic that bypasses TLS verification. - Disable or reject plaintext HTTP access instead of relying solely on redirects, because the credential may already be exposed before a redirect is processed.
- Rotate all API tokens that may previously have been transmitted through the plaintext endpoint.
- Use short-lived, revocable, least-privilege tokens and apply server-side rate limits and anomaly detection.
- Avoid persisting tokens directly in shell startup files where practical. Prefer an operating-system credential store, secret manager, or protected configuration file with restrictive permissions.
- Update every example in
SKILL.mdand verify through automated checks that no credential-bearing request can use a non-TLS URL.
- Replace every
