CVE-2017-18871 — mattermost-server
HIGHCVE-2017-18871 is a high-severity (CVSS 7.5) vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.
Mattermost Server vulnerable to Denial of Service through `@` character prefix inserted into JavaScript field names
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Mattermost Server before 4.5.0, 4.4.5, 4.3.4, and 4.2.2. It allows attackers to cause a denial of service (application crash) via an @ character before a JavaScript field name.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 4.2.2go get github.com/mattermost/mattermost-server@v4.2.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.3.0-rc1&&< 4.3.4 | 4.3.4go get github.com/mattermost/mattermost-server@v4.3.4 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.4.0-rc1&&< 4.4.5 | 4.4.5go get github.com/mattermost/mattermost-server@v4.4.5 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.5.0-rc1&&< 4.5.0 | 4.5.0go get github.com/mattermost/mattermost-server@v4.5.0 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 4.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18871 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2017-18871 in your dependencies?
Find it across Go, including transitive dependencies.