CVE-2017-18884 — mattermost-server
HIGHCVE-2017-18884 is a high-severity (CVSS 8.1) Improper Privilege Management 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 exposes OAuth personal access tokens to attackers
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-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.3.0, 4.2.1, and 4.1.2. It allows attackers to gain privileges by using a registered OAuth application with personal access tokens.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 4.1.2go get github.com/mattermost/mattermost-server@v4.1.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.2.0-rc1&&< 4.2.1 | 4.2.1go get github.com/mattermost/mattermost-server@v4.2.1 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.3.0-rc1&&< 4.3.0 | 4.3.0go get github.com/mattermost/mattermost-server@v4.3.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.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18884 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2017-18884 in your dependencies?
Find it across Go, including transitive dependencies.