T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:68- Finding
Excessive Personal Data Collection for Roommate Advice
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 68 and 199-202
Vulnerability Type: Excessive collection and external transmission of personal data
Risk Level: MediumEvidence
The relevant source text, translated into English, states:
markdown Before starting: When this service API is invoked, personal information about the subject—including date of birth (and time), gender, place of birth, and current location—is sent to the Xinjianxue API (`chinaapi.xinjianxue.com`) for processing.markdown - Complete input: subject's date and time of birth, gender, place of birth (country and province/region/city), and current location. - Basic input: subject's date of birth, gender, and current location. - Both input levels require gender, date of birth, and the subject's current location (country and province/region/city). - Complete input additionally requires exact birth hour and minute and place of birth (country and province/region/city).Technical Analysis
The Skill provides guidance about roommate communication, boundaries, household rules, and conflict resolution. These functions do not inherently require a subject's date of birth, gender, birthplace, birth time, or current geographic location.
Nevertheless, the Skill requires several of these attributes before calling an external report service. This violates the data-minimization and least-privilege principles by obtaining and transmitting personal information beyond what is reasonably necessary for the declared task. The disclosure and consent language reduces the risk of covert collection, but it does not establish why every mandatory field is proportionate or technically necessary.
The Skill also permits analysis of another person when the user claims that person consented. No mechanism directly verifies the other person's identity or consent, creating a risk that a user could submit a roommate's information ...[truncated 1430 chars]
- Remediation
View remediation
Remediation Suggestions
- Provide ordinary roommate communication and boundary-setting advice locally without collecting demographic or location information.
- Make the external report an optional feature rather than a prerequisite for receiving roommate advice.
- Explain separately why each requested field is needed, how it affects the report, and whether the service can operate without it.
- Remove mandatory collection of exact birth time, birthplace, gender, and precise current location unless necessity is documented and technically enforced.
- Use coarse location information where location is genuinely required, and avoid collecting province or city data by default.
- Obtain explicit, purpose-specific consent immediately before transmitting information to the external service.
- Do not submit another person's data based solely on an unverifiable assertion of consent. Prefer direct participation or independently recorded consent from each subject.
- Publish and technically enforce retention, deletion, access-control, and incident-response policies for submitted reports and request metadata.
- Ensure logs, telemetry, error responses, and conversation history do not retain birth details, location data, authorization codes, license keys, or API keys.
- Add a local fallback path when the user declines external processing or provides only the information necessary to describe the roommate conflict.
