Security Resilience

CVE-2024-1402

DoS in Mattermost Server ≤ 8.1.7

Published
09 February 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0052 43th percentile
Risk Priority 37 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-1402 is a medium-severity Uncontrolled Resource Consumption (CWE-400) vulnerability in Mattermost Mattermost Server. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 43th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-5 (Denial-of-service Protection) and SC-6 (Resource Availability) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-3116Same product: Mattermost Mattermost Server
CVE-2023-45847Same product: Mattermost Mattermost Server
CVE-2026-26233Same product: Mattermost Mattermost Server
CVE-2026-5308Same product: Mattermost Mattermost Server
CVE-2024-24988Same product: Mattermost Mattermost Server
CVE-2026-5755Same product: Mattermost Mattermost Server
CVE-2023-3593Same product: Mattermost Mattermost Server
CVE-2023-3614Same product: Mattermost Mattermost Server
CVE-2024-47003Same product: Mattermost Mattermost Server
CVE-2023-49809Same product: Mattermost Mattermost Server

Affected Assets

mattermost
mattermost server
≤ 8.1.7 · 9.0.0 — 9.1.4 · 9.2.0 — 9.2.3

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-5 directly limits the effects of resource-exhaustion events that constitute uncontrolled consumption.

SC-6 enforces explicit allocation limits on resources, structurally preventing the weakness from occurring.

Process isolation confines resource consumption to separate domains, reducing blast radius without stopping the root flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Pre-agreed severity-based prioritization and resource allocation during incident triage reduce the likelihood that an attacker-induced resource exhaustion will overwhelm the organization before corrective action is taken.

finds

Early notification of anomalous resource consumption or system malfunctions enables throttling or isolation before availability is lost.

A.8.15 Logging partial match
finds

Specifying log storage limits and rotation procedures reduces the risk that unbounded log growth will exhaust disk or memory resources and cause denial of service.

finds

Resource-utilization monitoring and alerting on bottlenecks or overloads limits the impact of denial-of-service or resource-exhaustion attacks.

blocks

A.8.20 implements network-level protections (firewalls, segmentation, protocol hardening, monitoring, authentication of systems/devices) that can limit abuse of a resource-consuming weakness but do not stop the weakness from being exploitable; the flaw remains present in the product and can still be triggered from an authorized or internal context.

blocks

Monitoring network service usage and applying controls to restrict access when necessary limits an attacker’s ability to consume excessive resources through unrestricted or unauthenticated service calls.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-400, a class-level weakness. Rules are authored against its narrower children: CWE-770.

References