提出 #852962: Sipeed PicoClaw <= 0.2.9 Incorrect Authorization (CWE-863)情報

タイトルSipeed PicoClaw <= 0.2.9 Incorrect Authorization (CWE-863)
説明# Technical Details An authorization and policy bypass exists in the WeCom inbound channel in `pkg/channels/wecom/wecom.go` of PicoClaw. The application fails to enforce the configured group trigger policy before publishing WeCom group messages to the internal inbound bus. `dispatchIncoming` classifies `body.chattype="group"` as a group message, but directly calls `HandleInboundContext` without invoking the shared `ShouldRespondInGroup` gate. # Vulnerable Code File: `pkg/channels/wecom/wecom.go` Method: `handleMessageCallback`, `dispatchIncoming` Why: Accepts ordinary WeCom message callbacks and forwards group messages to `HandleInboundContext` without checking `group_trigger.mention_only`. File: `pkg/channels/base.go` Method: `ShouldRespondInGroup` Why: Implements the expected mention-only group gate, but WeCom fails to invoke it before publishing inbound messages. # Reproduction 1. Configure WeCom with `channels.wecom.group_trigger.mention_only=true`. 2. Send an ordinary unmentioned WeCom group message. 3. Observe `dispatchIncoming` sets `ChatType` to `group` and publishes the content to `MessageBus.InboundChan`. 4. Run the control gate and observe that `ShouldRespondInGroup` would suppress the message. # Impact - Allows unmentioned WeCom group messages to reach the agent runtime despite mention-only policy. - Enables unauthorized prompt injection by ordinary group participants. - May trigger unintended tools, workflow actions, or model/API resource consumption.
ソース⚠️ https://github.com/sipeed/picoclaw/issues/3076
ユーザー
 Eric-i (UID 97584)
送信2026年06月09日 13:33 (1 月 ago)
モデレーション2026年07月18日 09:22 (1 month later)
ステータス承諾済み
VulDBエントリ380011 [Sipeed PicoClaw 迄 0.2.9 Group Message wecom.go dispatchIncoming 特権昇格]
ポイント20

Want to stay up to date on a daily basis?

Enable the mail alert feature now!