CVE-2022-31017
First published: Sat Jun 25 2022(Updated: )
Zulip is an open-source team collaboration tool. Versions 2.1.0 through and including 5.2 are vulnerable to a logic error. A stream configured as private with protected history, where new subscribers should not be allowed to see messages sent before they were subscribed, when edited causes the server to incorrectly send an API event that includes the edited message to all of the stream’s current subscribers. This API event is ignored by official clients, but can be observed by using a modified client or the browser’s developer tools. This bug will be fixed in Zulip Server 5.3. There are no known workarounds.
Credit: security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Zulip Zulip | >=2.1.0<5.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2022-31017?
The severity of CVE-2022-31017 is low with a CVSS score of 2.6.
How does CVE-2022-31017 affect Zulip?
CVE-2022-31017 affects Zulip versions 2.1.0 through 5.2.
What is the vulnerability in Zulip?
The vulnerability in Zulip is a logic error that occurs when editing a private stream with protected history.
How can I fix CVE-2022-31017 in Zulip?
To fix CVE-2022-31017 in Zulip, update to a version higher than 5.2.
Where can I find more information about CVE-2022-31017?
More information about CVE-2022-31017 can be found in the Zulip GitHub security advisory.
- collector/nvd-index
- vendor/zulip
- canonical/zulip zulip
- version/zulip zulip/2.1.0