T05 · Unauthorized Access and Privilege Escalation
- Location
SKILL.md:21- Finding
Private Workspace Data May Be Copied and Disclosed Through Unvalidated Fixed Destinations
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 21–26, 30–34, 62–67, and 73
Vulnerability Type: Excessive private-data access and insecure destination configuration
Risk Level: HighVulnerable Code
markdown **Slack** (`slack_search_public_and_private`): - 今日自分が送ったメッセージ・参加したスレッド(`from:me after:today`) - 今日決まったこと・アクションアイテム **DM チャット** (`aachat_read_messages`): - `dm:phase1demo.p-take55` の今日のやりとり(朝のブリーフィング内容・追加の依頼・完了報告)markdown 環境変数 `NOTION_DAILY_JOURNAL_PAGE_ID` が設定されていればその親ページ(またはデータベース)を使う。未設定なら `notion-search` で "日報" や "Daily Log" を検索して特定する。 その日の日報ページが既にあれば `notion-update-page` で追記、なければ `notion-create-pages` で新規作成: - タイトル: `{YYYY-MM-DD} 日報` - 親: 上で特定したページまたはデータベースmarkdown `aachat_send_message` で `dm:phase1demo.p-take55` に投稿:Notion 日報を更新しました: {YYYY-MM-DD} {Notion ページ URL}
text markdown - Slack・DM のプライベートな内容も個人ノート扱いで Notion に書いてよいTechnical Analysis
The skill explicitly searches public and private Slack content, reads a fixed direct-message conversation, and authorizes private Slack and DM information to be written into Notion. This collection scope is broader than the minimum access needed for a daily journal and lacks per-source consent, sensitivity filtering, or a preview-and-confirmation step.
The destination controls are also unsafe:
- If
NOTION_DAILY_JOURNAL_PAGE_IDis unavailable, the skill selects a destination through a title search for generic names such asDaily Log. It does not require confirmation that the selected page belongs to the invoking user or has an appropriate sharing policy. - The source DM and notification recipient are hard-coded as
dm:phase1demo.p-take55, rather than being derived from the authenticated user or invocation context. - The resulting Notion page URL is sent to that fixed recipient without validating that the recipient is authorized to receive it.
Consequently, installing o ...[truncated 1884 chars]
- If
- Remediation
View remediation
Remediation Suggestions
- Remove the hard-coded
dm:phase1demo.p-take55identifier. Derive both the source conversation and notification recipient from the authenticated invoking user and validated runtime context. - Require explicit user approval before reading private channels or direct messages. Default collection to content authored by the user and to public sources.
- Allow the user to select individual sources and exclude channels, conversations, message types, or sensitivity classes.
- Require an explicitly configured and validated
NOTION_DAILY_JOURNAL_PAGE_ID. Do not automatically write to a page selected only through a generic title search. - If destination search remains supported, display all candidates and require user confirmation after showing page ownership, workspace, parent hierarchy, and sharing scope.
- Verify that the selected Notion destination is owned by or exclusively authorized for the invoking user before writing private information.
- Generate a preview of the proposed journal entry and require confirmation before transferring private Slack or DM content to Notion.
- Add redaction for credentials, personal data, confidential links, customer information, and other sensitive content.
- Validate the notification recipient immediately before sending the page URL, and avoid including the URL when recipient authorization cannot be established.
- Record auditable metadata identifying the approved sources, destination, invoking identity, and notification recipient without logging message contents or secrets.
- Remove the hard-coded
