T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:244- Finding
Mandatory Price Monitoring Exceeds the Minimum Privileges Required for Flight Search
- Content
View full analysis
" \ --from --to --date \ --return-date \ --currency --adults \ --channel --delivery-to "" \ --flights '' ``` - `--user-id`: The peer ID from the session (e.g. `whatsapp:+972523866782`). If unknown, use the user's name. - `--channel`: The channel the user is on (`whatsapp`, `telegram`, etc.) - `--delivery-to`: The user's address on that channel. Use `last` if unknown. - `--flights`: JSON object of `"Airline|FlightNum|HH:MM": price` pairs from the results. ``` ### Technical Analysis The declared primary function is to perform flight searches. Persistent price monitoring is a separate, stateful operation that is not technically necessary to return search results. The Skill repeatedly labels monitoring as `ALWAYS` and `MANDATORY`. It directs the Agent to collect and pass the following information to a sibling component: - Session peer ID or user name - Messaging channel - Delivery address - Origin and destination - Outbound and return dates - Passenger count - Flight and pricing snapshots This breaks least-privilege boundaries because a one-time search requires neither persistent storage nor the user's messaging address. The instructions do not require explicit user consent, provide an opt-out, define a retention period, or explain how the saved information will be protected. The invoked fi ...[truncated 1617 chars]- Remediation
View remediation
