other
- Location
my_task.py:4- Finding
Undisclosed Third-Party Network Access
- Content
View full analysis
Vulnerability Details
File Location:
my_task.py:4-5, 10-11; network behavior is not disclosed inSKILL.md:13-43
Vulnerability Type: Undisclosed External Network Access
Risk Level: LowVulnerable Code
python MAP_API = "https://sanjiaozhou.fushisanlang.cn/api/random_map_status" ARM_API = "https://sanjiaozhou.fushisanlang.cn/api/random_arm_equipment" # ... map_data = requests.get(MAP_API).json()[0] arm_data = requests.get(ARM_API).json()[0]Technical Analysis
Each execution contacts two endpoints hosted on the custom third-party domain
sanjiaozhou.fushisanlang.cn. The documentation describes the skill as a random map and equipment generator but does not disclose that its data is retrieved from an external service.Although HTTPS protects data in transit, the remote operator receives ordinary connection metadata such as the user's public IP address and request timing. The service also controls the data incorporated into the skill's output. The code does not validate HTTP status codes, content types, response size, or response structure beyond accessing expected fields.
The retrieved content is only formatted as text; it is not evaluated or executed. Therefore, this does not constitute remote payload execution.
Attack Path
- A user installs and runs the skill based on its documented random-generation functionality.
- The skill silently sends two HTTPS requests to the custom third-party service.
- The service observes the user's connection metadata.
- If the service or its infrastructure is compromised, an attacker can return manipulated JSON values.
- Those values are incorporated into the generated result and presented to the user.
Impact Assessment
The issue exposes network metadata to an inadequately disclosed third party and creates an integrity dependency on that service. A compromised service can manipulate displayed map, equipment, or weapon-code data wit ...[truncated 188 chars]
- Remediation
View remediation
Remediation Suggestions
- Clearly document both external endpoints, the reason for contacting them, and the associated privacy implications.
- Prefer a local, versioned dataset if remote access is unnecessary for the random-generation feature.
- If remote access is retained, use an approved and documented service with an appropriate privacy policy.
- Call
response.raise_for_status()before parsing each response. - Validate the response content type, maximum size, JSON schema, and expected value types before incorporating data into output.
- Consider restricting accepted response fields and lengths to reduce the effect of malicious or malformed server responses.
