GHSA-r67m-mf7v-qp7j CVE-2023-5968
Mattermost password hash disclosure vulnerability
Medium
Go
- Severity
- 4.9 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.51%
- Chance of exploitation in the next 30 days. Higher than 43.56% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-116 Improper Encoding or Escaping of Output
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Fix
- Available
- 4 packages have a fixed version
Description
Mattermost fails to properly sanitize the user object when updating the username, resulting in the password hash being included in the response body.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server | < 5.3.2-0.20230825233148-f787fd63368a |
5.3.2-0.20230825233148-f787fd63368a |
| github.com/mattermost/mattermost-server/v5 | < 5.3.2-0.20230825233148-f787fd63368a |
5.3.2-0.20230825233148-f787fd63368a |
| github.com/mattermost/mattermost-server/v6 | >= 5.4.0-rc1, < 7.8.12 |
7.8.12 |
| github.com/mattermost/mattermost-server/v6 | < 5.3.2-0.20230825233148-f787fd63368a |
5.3.2-0.20230825233148-f787fd63368a |
| github.com/mattermost/mattermost/server/v8 | >= 8.0.0, < 8.0.4 |
8.0.4 |
| github.com/mattermost/mattermost/server/v8 | >= 8.1.0, < 8.1.3 |
8.1.3 |
| github.com/mattermost/mattermost/server/v8 | >= 9.0.0, < 9.0.1 |
9.0.1 |
| github.com/mattermost/mattermost/server/v8 | < 8.0.0-20230825233148-f787fd63368a |
8.0.0-20230825233148-f787fd63368a |
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 → 5.3.2-0.20230825233148-f787fd63368a
- go
go get github.com/mattermost/mattermost-server@v5.3.2-0.20230825233148-f787fd63368a && go mod tidy
github.com/mattermost/mattermost-server/v5 Go → 5.3.2-0.20230825233148-f787fd63368a
- go
go get github.com/mattermost/mattermost-server/v5@v5.3.2-0.20230825233148-f787fd63368a && go mod tidy
github.com/mattermost/mattermost-server/v6 Go → 7.8.12
- go
go get github.com/mattermost/mattermost-server/v6@v7.8.12 && go mod tidy
github.com/mattermost/mattermost/server/v8 Go → 8.0.4
- go
go get github.com/mattermost/mattermost/server/v8@v8.0.4 && go mod tidy
Severity breakdown
CVSS 3.1 4.9
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-116: Improper Encoding or Escaping of Output
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
How to prevent it
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using the ESAPI Encoding control [REF-45] or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error. Alternately, use built-in functions, but consider using wrappers in case those functions are discovered to have a vulnerability.
- Architecture and Design: If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated. For example, stored procedures can enforce database query structure and reduce the likelihood of SQL injection.
- Architecture and Design, Implementation: Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages. Study all expected communication protocols and data representations to determine the required encoding strategies.
- Architecture and Design: In some cases, input validation may be an important strategy when output encoding is not a complete solution. For example, you may be providing the same output that will be processed by multiple consumers that use different encodings or representations. In other cases, you may be required to allow user-supplied input to contain control information, such as limited HTML tags that support formatting in a wiki or bulletin board. When this type of requirement must be met, use an extremely strict allowlist to limit which control sequences can be used. Verify that the resulting syntactic structure is what you expect. Use your normal encoding methods for the remainder of the input.
- Architecture and Design: Use input validation as a defense-in-depth measure to reduce the likelihood of output encoding errors (see CWE-20).
- Requirements: Fully specify which encodings are required by components that will be communicating with each other.
- Implementation: When exchanging data between components, ensure that both components are using the same character encoding. Ensure that the proper encoding is applied at each interface. Explicitly set the encoding you are using whenever the protocol allows you to do so.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
How to prevent it
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why 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 |
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