GHSA-379p-37xc-q963 CVE-2016-11076 GO-2025-4054
Mattermost Server does not check if cookies are used over SSL
- Severity
- 7.5 / 10
- High · CVSS 3.1
- Exploit chance (EPSS)
- 0.88%
- Chance of exploitation in the next 30 days. Higher than 59.09% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-295 Improper Certificate Validation
- CWE-614 Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
- Fix
3.0.0- Upgrade github.com/mattermost/mattermost-server to this version or later
Description
An issue was discovered in Mattermost Server before 3.0.0. It does not ensure that a cookie is used over SSL.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server | < 3.0.0 |
3.0.0 |
| github.com/mattermost/mattermost-server | < 3.0.0+incompatible |
3.0.0+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.0.0
- go
go get github.com/mattermost/mattermost-server@v3.0.0 && go mod tidy
Severity breakdown
CVSS 3.1 7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-295: Improper Certificate Validation
The product does not validate, or incorrectly validates, a certificate.
How to prevent it
- Architecture and Design, Implementation: Certificates should be carefully managed and checked to assure that data are encrypted with the intended owner's public key.
- Implementation: If certificate pinning is being used, ensure that all relevant properties of the certificate are fully validated before the certificate is pinned, including the hostname.
CWE-614: Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
How to prevent it
- Implementation: Always set the secure attribute when the cookie should be sent via HTTPS only.
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