T09 · Insecure Skill Coding Practices
- Location
knowledge/domain.md:13- Finding
Unencrypted arXiv API Transport Permits Search Result Manipulation
- Content
View full analysis
Vulnerability Details
File Location:
knowledge/domain.md, lines 13-18
Vulnerability Type: Use of an unencrypted HTTP endpoint
Risk Level: LowVulnerable Code
markdown ### API Endpoint - **Base URL**: `http://export.arxiv.org/api/query` - **Method**: GET - **Rate Limit**: 1 request per 3 seconds (be respectful; no authentication required)Technical Analysis
The Skill explicitly instructs the Agent to query the arXiv API through cleartext HTTP. HTTP does not provide transport confidentiality, server authentication, or response integrity.
An attacker with a network-level interception position could observe academic search terms or modify the returned Atom feed. Modified fields could include paper titles, authors, abstracts, identifiers, and links. Because the workflow subsequently screens, ranks, and summarizes this metadata, manipulated records could enter the final literature review.
Cleartext arXiv links also appear in sample response data at
knowledge/domain.md:63andknowledge/domain.md:71. Those examples reinforce the use of insecure transport but are not the primary API configuration.Attack Path
- The Agent follows the documented endpoint and submits an arXiv query over HTTP.
- An attacker capable of intercepting network traffic observes the request.
- The attacker alters the HTTP response before it reaches the Agent.
- The modified metadata is processed by the Skill's screening, citation-analysis, and ranking workflow.
- The Agent may present inaccurate citations, fabricated paper metadata, or substituted links to the user.
Impact Assessment
The issue does not grant local system privileges, code execution, persistent access, or credential access. The affected scope is limited primarily to the confidentiality of academic search queries and the integrity of arXiv search results.
Successful exploitation could undermine bibliographic accuracy, contaminate ...[truncated 71 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace the cleartext endpoint with HTTPS:
markdown - **Base URL**: `https://export.arxiv.org/api/query` -
Update the example response links at
knowledge/domain.md:63andknowledge/domain.md:71to use HTTPS. -
Require HTTPS for all academic database requests and retrieved document links.
-
Reject or warn on redirects that downgrade a request from HTTPS to HTTP.
-
Validate returned identifiers and links against expected arXiv formats and trusted hostnames before including them in results.
-
Cross-check important bibliographic metadata against an independent source, such as Semantic Scholar, before presenting it as verified.
-