T09 · Insecure Skill Coding Practices
- Location
SKILL.md:22- Finding
Unauthenticated RSS Transport Permits Content Tampering
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:22-25, 51-56
Vulnerability Type: Plaintext HTTP transport for external RSS feeds
Risk Level: MediumVulnerable Code
markdown | Quantum Physics | http://export.arxiv.org/rss/quant-ph | | Optics | http://export.arxiv.org/rss/physics.optics | | Instrumentation and Detectors | http://export.arxiv.org/rss/physics.ins-det | | Atomic Physics | http://export.arxiv.org/rss/physics.atom-ph |markdown | PRX Quantum | http://feeds.aps.org/rss/recent/prxquantum.xml | | Physical Review X | http://feeds.aps.org/rss/recent/prx.xml | | Physical Review Letters | http://feeds.aps.org/rss/recent/prl.xml | | Physical Review A | http://feeds.aps.org/rss/recent/pra.xml | | Physical Review B | http://feeds.aps.org/rss/recent/prb.xml | | Physical Review Research | http://feeds.aps.org/rss/recent/prresearch.xml |Technical Analysis
The Skill directs the Agent to retrieve several RSS feeds over unencrypted, unauthenticated HTTP. HTTP provides neither transport confidentiality nor server authenticity and does not protect content integrity against an on-path attacker.
An attacker able to intercept or modify network traffic can alter RSS titles, descriptions, links, authorship data, and other metadata before the Agent receives them. The workflow subsequently filters this remote content, summarizes it, and writes it into persistent paper notes and dashboards. The Skill also provides no explicit instruction to treat feed fields as untrusted data or to ignore instructions embedded in retrieved content.
This does not constitute remote code execution by itself. However, it creates a content-injection boundary through which fabricated research information, malicious links, or prompt-like text may enter generated artifacts.
Attack Path
...[truncated 1318 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace every
http://feed URL with a publisher-verifiedhttps://endpoint. - Reject redirects that downgrade from HTTPS to HTTP.
- Restrict feed retrieval to an explicit allowlist of expected schemes and hostnames.
- Validate TLS certificates using the platform's trusted certificate store; do not disable certificate or hostname verification.
- Treat all RSS fields as untrusted data. Explicitly instruct the Agent not to execute commands, follow operational instructions, or change behavior based on feed content.
- Sanitize generated Markdown links and reject unsafe URI schemes before persisting them.
- Where available, verify paper identifiers, titles, and destination links against canonical publisher metadata.
- Record retrieval failures rather than falling back to plaintext transport.
- Replace every
