other
- Location
scripts/marketing_hub.js:348- Finding
Bearer Credential Transmitted to an Undeclared and Non-Allowlisted Host
- Content
View full analysis
v.aweme_info?.product_info?.product_id); return videos; } ``` The same destination and authorization header are used by `douyinSearchUser()` and `douyinUserVideos()`. The manifest instead declares: ```yaml permissions: network_mode: allowlist allowed_hosts: - www.douyin.com - douyin.com - api.tikhub.io - api.deepseek.com clientPermissions: network: httpsOutbound: true documentedHosts: - api.tikhub.io - api.deepseek.com ``` ### Technical Analysis The implementation reads `TIKHUB_TOKEN` from the environment or a legacy configuration file and places it in an HTTP `Authorization: Bearer` header sent to `api.tikhub.dev`. The manifest only authorizes and documents `api.tikhub.io`. The audited project provides no evidence establishing that the undeclared `.dev` hostname is an approved alias or is controlled by the intended API provider. This therefore constitutes sensitive credent ...[truncated 1117 chars]- Remediation
View remediation
