T09 · Insecure Skill Coding Practices
- Location
dashboard-kit/DASHBOARD-SPEC.md:120- Finding
Dashboard specification contradicts local-only privacy guarantees by synchronizing sensitive travel data to Supabase
- Content
View full analysis
Vulnerability Details
File Location:
dashboard-kit/DASHBOARD-SPEC.md:120-194, 296-301;dashboard-kit/manifest.json:20-36
Vulnerability Type: Undisclosed external synchronization of sensitive travel information
Risk Level: MediumVulnerable Code
sql -- User travel profile CREATE TABLE travel_profiles ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), user_id UUID REFERENCES auth.users NOT NULL, pace_preference VARCHAR(20) DEFAULT 'balanced', budget_style VARCHAR(20) DEFAULT 'value', hotel_style VARCHAR(50), dietary_needs TEXT, home_airport VARCHAR(10), passport_valid_through DATE, travel_pet_peeves TEXT[], learned_preferences JSONB DEFAULT '{}', past_destinations TEXT[] DEFAULT '{}', bucket_list TEXT[] DEFAULT '{}', created_at TIMESTAMPTZ DEFAULT NOW(), updated_at TIMESTAMPTZ DEFAULT NOW() );sql -- Loyalty programs CREATE TABLE loyalty_programs ( id UUID PRIMARY KEY DEFAULT gen_random_uuid(), profile_id UUID REFERENCES travel_profiles(id) ON DELETE CASCADE NOT NULL, program VARCHAR(100) NOT NULL, tier VARCHAR(50), member_number VARCHAR(50) );text ## Data Sync The dashboard reads from the same data the chat agent writes: - Chat → Dashboard: Agent writes trip JSON files. Dashboard import script reads these and upserts into Supabase. - Dashboard → Chat: User checks packing items or logs expenses in the dashboard. Agent reads updated state on next interaction. - Sync script: A lightweight Node.js script that watches `travel/trips/` for changes and syncs to Supabase. Runs as a background process or on-demand.The dashboard manifest also defines fields for booking confirmation numbers and loyalty membership numbers:
json {"name":"confirmation_number","type":"TEXT"}json {"name":"member_number","type":"TEXT"}Technical Analysis
...[truncated 2714 chars]
- Remediation
View remediation
Remediation Suggestions
- Make cloud synchronization disabled by default and require explicit, informed opt-in before transmitting any records.
- Correct
README.mdandSECURITY.mdso they distinguish local core functionality from the optional cloud dashboard. - Display the destination service, transmitted fields, retention policy, deletion procedure, and applicable third-party privacy terms before consent.
- Apply data minimization:
- Do not synchronize passport-expiry information.
- Remove confirmation numbers and loyalty member numbers from the remote schema.
- Avoid synchronizing precise itinerary details unless essential.
- Use opaque local references instead of account identifiers.
- Allow users to select which trips and fields may be synchronized.
- Encrypt sensitive fields before upload with keys unavailable to the backend.
- Implement complete row-level security policies using both
USINGandWITH CHECKexpressions for all operations. - Use least-privilege Supabase credentials and never expose service-role keys to client code.
- Add automated cross-account isolation tests, deletion tests, audit logging, and incident-response procedures.
- Avoid a persistent filesystem watcher where on-demand synchronization can satisfy the feature.
