T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:29
- Finding
- Unverified, Misidentified, and Insecure RSS Sources<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md`, lines 29-35 **Vulnerability Type**: Untrusted third-party content sources and plaintext RSS transport **Risk Level**: Medium ### Complete Code Snippet ```markdown | AP News | https://rsshub.app/apnews/topics/apf-topnews | EN | ### 国内新闻(中文) | 来源 | RSS URL | 语言 | |------|---------|------| | 新华网 | https://www.rss臆.com/xml/Rss臆news.xml | ZH | | 人民网 | http://www.people.com.cn/rss/news.xml | ZH | ``` ### Technical Analysis The skill presents these endpoints as authoritative publisher feeds, but their trust properties are inadequate: - The AP News entry uses `rsshub.app`, a third-party aggregation service, rather than an AP-controlled domain. Compromise or manipulation of that intermediary could alter content attributed to AP. - The purported Xinhua endpoint uses the anomalous Unicode domain `www.rss臆.com`, which is not an official Xinhua domain. This resembles a misidentified or potentially deceptive source. - The People's Daily endpoint uses plaintext HTTP. A network-positioned attacker could intercept or modify the response because transport authenticity and integrity are not protected. RSS data is external, attacker-influenceable input. If an agent treats feed titles or descriptions as trusted instructions rather than inert news content, malicious feed data could also attempt indirect prompt injection. Even without instruction execution, manipulated content can be incorporated into generated briefings and falsely attributed to trusted publishers. ### Attack Path 1. An attacker controls or compromises a listed third-party endpoint, controls the anomalous domain, or obtains a network position capable of intercepting the plaintext HTTP feed. 2. The attacker returns fabricated titles, links, descriptions, or instruction-like text in a syntactically valid RSS document. 3. The skill retrieves the content while treating the endpoint as a trusted news source. 4. The agent summarizes or republishes t ...[truncated 878 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Replace every feed with a verified, publisher-controlled HTTPS endpoint. 2. Remove the anomalous `www.rss臆.com` endpoint unless ownership and authenticity can be independently established. 3. Clearly identify third-party aggregators as intermediaries rather than presenting them as first-party feeds. 4. Replace the plaintext People's Daily URL with a verified HTTPS endpoint. Remove it if HTTPS is unavailable. 5. Maintain an allowlist of expected schemes and hostnames, and validate the final connection hostname before processing content. 6. Reject non-HTTPS feeds and unexpected cross-domain redirects. 7. Parse RSS with a hardened XML parser that disables external entities and applies response-size and processing limits. 8. Treat every feed field as untrusted data. Do not interpret titles, descriptions, or linked content as agent instructions. 9. Preserve source provenance in generated reports so users can distinguish first-party feeds from aggregators. 10. Periodically verify endpoint ownership, certificate validity, availability, and content consistency. ]]>
