Skip to content

GHSA-34cx-hvm4-vx7j CVE-2017-18908 GO-2026-4476

Mattermost Server password reset email requests can be sent to attacker-provided email addresses

Critical Go
Severity
9.8 / 10
Critical · CVSS 3.1
Exploit chance (EPSS)
1.18%
Chance of exploitation in the next 30 days. Higher than 67.81% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
CWE-640 Weak Password Recovery Mechanism for Forgotten Password
Fix
3.9.1-rc1
Upgrade github.com/mattermost/mattermost-server to this version or later

Description

An issue was discovered in Mattermost Server before 4.0.0, 3.10.1, and 3.9.1. A password reset request was sometimes sent to an attacker-provided e-mail address.

Affected versions

Go

PackageVulnerableFixed in
github.com/mattermost/mattermost-server
< 3.9.1-rc1
3.9.1-rc1
github.com/mattermost/mattermost-server
>= 3.10.0, < 3.10.1
3.10.1
github.com/mattermost/mattermost-server
< 3.9.1-rc1+incompatible
>= 3.10.0+incompatible, < 3.10.1+incompatible
3.9.1-rc1+incompatible
3.10.1+incompatible

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/mattermost/mattermost-server Go → 3.9.1-rc1

go
go get github.com/mattermost/mattermost-server@v3.9.1-rc1 && go mod tidy

Severity breakdown

CVSS 3.1 9.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

CWE-640: Weak Password Recovery Mechanism for Forgotten Password

The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

How to prevent it
  • Architecture and Design: Make sure that all input supplied by the user to the password recovery mechanism is thoroughly filtered and validated.
  • Architecture and Design: Do not use standard weak security questions and use several security questions.
  • Architecture and Design: Make sure that there is throttling on the number of incorrect answers to a security question. Disable the password recovery functionality after a certain (small) number of incorrect guesses.
  • Architecture and Design: Require that the user properly answers the security question prior to resetting their password and sending the new password to the e-mail address of record.
  • Architecture and Design: Never allow the user to control what e-mail address the new password will be sent to in the password recovery mechanism.
  • Architecture and Design: Assign a new temporary password rather than revealing the original password.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-xmfh-3ccg-c9fx
Mattermost has an Incorrect Authorization issue
Low Also affects github.com/mattermost/mattermost-server
GHSA-h998-hxxj-8q83
Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation
Medium Also affects github.com/mattermost/mattermost-server
GHSA-g5vr-6pgg-74qv
Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint
Low Also affects github.com/mattermost/mattermost-server
GHSA-jqgv-39mg-7c2r
Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret
Medium Also affects github.com/mattermost/mattermost-server
GHSA-mxq2-5jpg-7474
Mattermost doesn't validate channel ownership of an existing subscription before applying edits
Medium Also affects github.com/mattermost/mattermost-server
GHSA-2g8v-grq3-hq2g
Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler
Medium Also affects github.com/mattermost/mattermost-server
GHSA-6hxm-w4hv-vgvw
Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints
High Also affects github.com/mattermost/mattermost-server
GHSA-9p44-r552-4wp9
Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations
Medium Also affects github.com/mattermost/mattermost-server
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor