LobeChat 2.2.1 Webhook Signature Verification Bypass QQ Feishu
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| lobehub | lobehub | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Lobehub | Lobehub |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.201% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | LobeChat (LobeHub) 2.2.1 does not properly verify inbound chat-platform webhook signatures in the QQ and Feishu adapters. The webhook route (/api/agent/webhooks/:platform) is unauthenticated by design and delegates verification to each adapter; the QQ adapter performs no Ed25519 signature verification on dispatched message events, and the Feishu adapter only performs an optional static-token comparison that is skipped when no token is configured (the default) and is not a body signature. An unauthenticated attacker who knows the public webhook URL can POST forged inbound messages with an attacker-chosen sender identity and arbitrary text, causing the bot owner's agent to process attacker-controlled input and treat the attacker as a trusted platform sender. | |
| Title | LobeChat 2.2.1 Webhook Signature Verification Bypass QQ Feishu | |
| First Time appeared |
Lobehub
Lobehub lobehub |
|
| Weaknesses | CWE-345 | |
| CPEs | cpe:2.3:a:lobehub:lobehub:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Lobehub
Lobehub lobehub |
|
| References |
|
|
| Metrics |
cvssV3_1
|