stoatchat before 0.15.0 Permission Bypass via message_fetch
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| stoatchat | stoatchat | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Stoatchat | Stoatchat |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.375% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Stoatchat
Stoatchat stoatchat |
|
| Vendors & Products |
Stoatchat
Stoatchat stoatchat |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | stoatchat before 0.15.0 contains a permission bypass vulnerability in the message_fetch route that checks only ViewChannel permission instead of requiring ReadMessageHistory. Attackers with ViewChannel access but ReadMessageHistory denied can retrieve individual message content by ID, bypassing the intended history restriction enforced by bulk read routes. | |
| Title | stoatchat before 0.15.0 Permission Bypass via message_fetch | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|