| Titre | Sipeed PicoClaw <= 0.2.9 Incorrect Authorization (CWE-863) |
|---|
| Description | # 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. |
|---|
| La source | ⚠️ https://github.com/sipeed/picoclaw/issues/3076 |
|---|
| Utilisateur | Eric-i (UID 97584) |
|---|
| Soumission | 09/06/2026 13:33 (il y a 1 mois) |
|---|
| Modérer | 18/07/2026 09:22 (1 month later) |
|---|
| Statut | Accepté |
|---|
| Entrée VulDB | 380011 [Sipeed PicoClaw jusqu’à 0.2.9 Group Message wecom.go dispatchIncoming élévation de privilèges] |
|---|
| Points | 20 |
|---|