T09 · Insecure Skill Coding Practices
- Location
SKILL.md:18- Finding
Untrusted Email Content Can Trigger Destructive Calendar Mutations Without Exact Event Validation
- Content
View full analysis
T00:00:00Z" --to "T23:59:59Z" --json`). - **Jidoka Stop:** Verify events are returned. IF no matching event is found, reply "No conflicting calendar events found" and STOP. Do NOT proceed. **Step 3: Reconcile State** - Execute the `Google Calendar Delete Event` atomic node or the `Google Calendar Update Summary` atomic node to append "[CANCELLED]". - **Jidoka Stop:** Verify the atomic node returns a success JSON response. IF it fails, retry the node up to 3 times with the exact error. IF it still fails, report the error to the user and STOP. **Step 4: Notify** - Inform the user that the calendar state has been successfully reconciled. ] ``` ### Technical Analysis The workflow treats email content as authoritative input and may begin merely when the agent reads an email indicating a cancellation or rescheduling. Although the extracted payload is nominally validated, the instructions do not define validation of the sender's authority, event identity, organizer, attendees, calendar, or immutable event ident ...[truncated 2472 chars]- Remediation
View remediation
