T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:86- Finding
Overbroad Access to Local Notifications
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 86–107
Vulnerability Type: T05: Unauthorized Access and Privilege Escalation
Risk Level: MediumVulnerable Instructions
text ### 3. Retrieve and refine fan group notifications If the user's request involves message notifications, fan groups, game viewing groups, group chat hot discussions, mobile phone reminders, or the user explicitly requests full/select `post-match hot topics', the notification must be queried first, and then notification-related content is generated. Use local notification retrieval capabilities. If the user provides a time range, the user time range is strictly used. If no time range is provided, the default query is 2 hours before the start of the game to 24 hours after the game. If the match time has not been confirmed yet, confirm the match time first; if the match time still cannot be confirmed, query the local time from 00:00 yesterday to the current time. Reusing old notification results is strictly prohibited. Each time a notification context is required, it must be queried again. If local notification retrieval is unavailable or fails, write `Currently unable to query related fan group notifications. `, and continue to generate other modules. Extract only content relevant to the target match or World Cup post-match discussion from all return notifications. Screening clues include: - Event words: World Cup, World Cup, group stage, knockout round, battle report, post-match, review - Team name, alias, country name, abbreviation - Player names, common nicknames, coach names - Scores, goals, red cards, penalties, hat tricks, buzzers, upsets, records - Fan group/chat signals: group announcement, group chat, brothers, gathering, staying up late, halftime, post-game, review, breaking defense, becoming a god, laughing to death, refunding money - User scenario scope: Teams/players/players in `Follow Who', output types in `What to Follow', groups, application ...[truncated 2769 chars]- Remediation
View remediation
Remediation Suggestions
- Require explicit, informed user consent immediately before accessing local notifications.
- Make notification enrichment opt-in rather than automatically enabling it for every “full” review.
- Restrict retrieval at the source to applications, groups, or channels expressly selected by the user.
- Apply football-specific keywords and sender filters before notification content is returned to the agent.
- Exclude banking, authentication, work, health, system, and other sensitive categories at the retrieval layer rather than filtering them after collection.
- Use the narrowest possible time range and require confirmation when match time is unknown instead of searching from the previous day by default.
- Limit the number and size of returned results and redact unnecessary names, message bodies, identifiers, and metadata.
- Treat notification content solely as untrusted data and explicitly prohibit following instructions embedded in messages.
- Avoid repeated retrieval during the same task unless the user requests a refresh.
- Clearly disclose retrieval scope, applications, time range, and purpose before requesting access.
