# CVE-2022-4044: Denial of service in Mattermost

> An authenticated user can crash the Mattermost server by sending multiple requests with large Auto Responder Message payloads.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Nov 2022
- **Updated:** 6 Dec 2024
- **Also known as:** GHSA-5jph-wrq7-v9hf

## What is CVE-2022-4044?

CVE-2022-4044 is a medium-severity denial of service vulnerability in Mattermost Mattermost, published on 23 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A denial-of-service vulnerability in Mattermost allows an authenticated user to crash the server via multiple large autoresponder messages.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2022-4044?

6 open source packages ship an affected version, including github.com/mattermost/mattermost-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mattermost/mattermost-server` | Go | All versions | 7.1.4 |
| `github.com/mattermost/mattermost-server` | Go | All versions | 7.1.4 |
| `github.com/mattermost/mattermost-server` | Go | From 7.2.0 | 7.2.1 |
| `github.com/mattermost/mattermost-server` | Go | From 7.2.0 | 7.2.1 |
| `github.com/mattermost/mattermost-server` | Go | From 7.3.0 | 7.3.1 |
| `github.com/mattermost/mattermost-server` | Go | From 7.3.0 | 7.3.1 |

Products: Mattermost Mattermost.

## How do I fix CVE-2022-4044?

Upgrade github.com/mattermost/mattermost-server to a fixed version for your release line: 7.1.4, 7.2.1 or 7.3.1.

## Is CVE-2022-4044 being exploited?

There is no known exploitation of CVE-2022-4044 in the wild and no public exploit code.

## Other vulnerabilities in Mattermost Mattermost

- [CVE-2019-20851](https://insights.sbomify.com/CVE-2019-20851/): Path traversal in n/a (critical 9.1)
- [CVE-2024-39274](https://insights.sbomify.com/CVE-2024-39274/): Malicious remote can add users to arbitrary teams and channels (high 8.7)
- [CVE-2024-39777](https://insights.sbomify.com/CVE-2024-39777/): Malicious remote can invite itself to an arbitrary local channel (high 8.7)
- [CVE-2024-39830](https://insights.sbomify.com/CVE-2024-39830/): Timing attack during remote cluster token comparison when shared channels are enabled (high 8.1)
- [CVE-2023-3615](https://insights.sbomify.com/CVE-2023-3615/): Lack of server certificate validation in websockets connection (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4044 and fix it if it is affected.

What it is: CVE-2022-4044 is a medium-severity denial of service vulnerability in Mattermost Mattermost, published on 23 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4044 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mattermost/mattermost-server (Go): affected all versions; fixed in 7.1.4
- github.com/mattermost/mattermost-server (Go): affected all versions; fixed in 7.1.4
- github.com/mattermost/mattermost-server (Go): affected from 7.2.0; fixed in 7.2.1
- github.com/mattermost/mattermost-server (Go): affected from 7.2.0; fixed in 7.2.1
- github.com/mattermost/mattermost-server (Go): affected from 7.3.0; fixed in 7.3.1
- github.com/mattermost/mattermost-server (Go): affected from 7.3.0; fixed in 7.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-4044/ (Markdown: https://insights.sbomify.com/CVE-2022-4044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-4044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-4044
- OSV: https://osv.dev/vulnerability/CVE-2022-4044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-4044/
Summaries are generated and may contain mistakes; the official description above is the record.