CVE-2024-1402
published 2024-02-09CVE-2024-1402: Mattermost fails to check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post…
PriorityP419medium4.3CVSS 3.1
AVNACLPRNUIRSUCNINAL
EPSS
0.52%
41.1th percentile
Mattermost fails to check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post, allowing an attacker sending a huge amount of non-existent custom emojis in a post to crash the mobile app of a user seeing the post and to crash the server due to overloading when clients attempt to retrive the aforementioned post.
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| github.com | mattermost_mattermost-server | >= 9.1.0+incompatible < 9.1.5+incompatible | 9.1.5+incompatible |
| github.com | mattermost_mattermost-server | >= 9.2.0+incompatible < 9.2.4+incompatible | 9.2.4+incompatible |
| github.com | mattermost_mattermost_server_v8 | >= 0 < 8.1.8 | 8.1.8 |
| github.com | mattermost_mattermost_server_v8 | >= 9.1.0 < 9.1.5 | 9.1.5 |
| github.com | mattermost_mattermost_server_v8 | >= 9.2.0 < 9.2.4 | 9.2.4 |
| mattermost | mattermost | <= 8.1.7 | — |
| mattermost | mattermost_server | <= 8.1.7 | — |
| mattermost | mattermost_server | 9.0.0 – 9.1.4 | — |
| mattermost | mattermost_server | 9.2.0 – 9.2.3 | — |
CVSS provenance
nvdv3.14.3MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Mattermost vulnerable to denial of service via large number of emoji reactions in github.com/mattermost/mattermost-server
osv·2024-06-28
CVE-2024-1402 Mattermost vulnerable to denial of service via large number of emoji reactions in github.com/mattermost/mattermost-server
Mattermost vulnerable to denial of service via large number of emoji reactions in github.com/mattermost/mattermost-server
Mattermost vulnerable to denial of service via large number of emoji reactions in github.com/mattermost/mattermost-server.
NOTE: The source advisory for this report contains additional versions that could not be automatically mapped to standard Go module versions.
(If this is causing false-positive reports from vulnerability scanners, please suggest an edit to the report.)
The additional affected modules and versions are: github.com/mattermost/mattermost/server/v8 before v8.1.8.
GHSA
Mattermost vulnerable to denial of service via large number of emoji reactions
ghsa·2024-02-09
CVE-2024-1402 [MEDIUM] CWE-400 Mattermost vulnerable to denial of service via large number of emoji reactions
Mattermost vulnerable to denial of service via large number of emoji reactions
Mattermost fails to check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post, allowing an attacker sending a huge amount of non-existent custom emojis in a post to crash the mobile app of a user seeing the post. Fetching posts with huge amounts of reactions results in Uncontrolled Resource Consumption.
OSV
Mattermost vulnerable to denial of service via large number of emoji reactions
osv·2024-02-09
CVE-2024-1402 [MEDIUM] Mattermost vulnerable to denial of service via large number of emoji reactions
Mattermost vulnerable to denial of service via large number of emoji reactions
Mattermost fails to check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post, allowing an attacker sending a huge amount of non-existent custom emojis in a post to crash the mobile app of a user seeing the post. Fetching posts with huge amounts of reactions results in Uncontrolled Resource Consumption.
Red Hat
kernel: blk-iocost: do not WARN if iocg was already offlined
vendor_redhat·2024-05-30·CVSS 5.5
CVE-2024-36908 [MEDIUM] CWE-20 kernel: blk-iocost: do not WARN if iocg was already offlined
kernel: blk-iocost: do not WARN if iocg was already offlined
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: do not WARN if iocg was already offlined
In iocg_pay_debt(), warn is triggered if 'active_list' is empty, which
is intended to confirm iocg is active when it has debt. However, warn
can be triggered during a blkcg or disk removal, if iocg_waitq_timer_fn()
is run at that time:
WARNING: CPU: 0 PID: 2344971 at block/blk-iocost.c:1402 iocg_pay_debt+0x14c/0x190
Call trace:
iocg_pay_debt+0x14c/0x190
iocg_kick_waitq+0x438/0x4c0
iocg_waitq_timer_fn+0xd8/0x130
__run_hrtimer+0x144/0x45c
__hrtimer_run_queues+0x16c/0x244
hrtimer_interrupt+0x2cc/0x7b0
The warn in this situation is meaningless. Since this iocg is being
removed, the state of the 'active_list' is ir
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2024-02-09
Published