Private-channel discovery via missing read check
Published Jun 19, 2020 · Updated Aug 4, 2024
Information disclosure in Mattermost Server before 5.19.0 allows attackers to discover private channels through the get-channel-by-name API. The getChannelByName handler retrieves a channel object from an attacker-supplied team identifier and channel name before enforcing the private-channel read check. A request must correctly name the target team and channel; exposure is limited to channel existence and returned metadata, not message contents.
Summary
What happened
Information disclosure in Mattermost Server before 5.19.0 allows attackers to discover private channels through the get-channel-by-name API. The getChannelByName handler retrieves a channel object from an attacker-supplied team identifier and channel name before enforcing the private-channel read check. A request must correctly name the target team and channel; exposure is limited to channel existence and returned metadata, not message contents.
The record
- CVE
- CVE-2020-14458
- Published
- Jun 19, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo