6 ms·
Zulip Cloud security vulnerability with reusable invitation links
- tommoor 5y agoFor anyone interested in the bug and fix: https://github.com/zulip/zulip/commit/7e991c8c7e59291296fecd3fa38e32d011249952 https://github.com/zulip/zulip/commit/7e991c8c7e59291296fecd...
- paulhart 5y agoMuch easier to read: https://blog.zulip.com/2022/02/25/zulip-cloud-invitation-vulnerability/ https://blog.zulip.com/2022/02/25/zulip-cloud-invitation-vul...
- deleted 5y ago[deleted]
- dang 5y agoChanged to that from https://cvepremium.circl.lu/cve/CVE-2022-21706 https://cvepremium.circl.lu/cve/CVE-2022-21706. Thanks!
- KennyBlanken 5y agohttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21706 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-2170... > Zulip Server version 2.0.0 and above are vulnerable to insufficient access control with multi-use invitations. A Zulip Server deployment which hosts multiple organizations is vulnerable to an attack where an invitation created in one organization (potentially as a role with elevated permissions) can be used to join any other organization. This bypasses any restrictions on required domains on users' email addresses, may be used to gain access to organizations which are only accessible by invitation, and may be used to gain access with elevated privileges. This issue has been patched in release 4.10. Why does it feel like the completely misleading title was intentional to try and drive traffic to / SEO this crappy copycat CVE site?
- mosselman 5y agoIs anyone using Zulip and has it made a difference to Slack for example?
- mavelikara 5y agoWe use Zulip at work. I have used Slack in a previous job. Zulip's interface looks a little clunkier than Slack, but I like Zulip.
- capableweb 5y agoClojurians-Zulip is much better interface to catch up and read through existing information than Clojurians-Slack ever was (Clojurians is basically bunch of Clojure(Script) people helping/getting help from each other), for whats it worth. Best would be if they both could be fully public, but for now the archives seems to do the job well at least.
- abhigyank 5y agoZulip is working on having public view of streams without having an account. It's already being experimently deployed on the Zulip Dev's server.So that should make its way to other consumer servers soon!
- temp 5y agoWe use it at work. We first switched over to Mattermost, then to Zulip. Mattermost seemed like a clone of Slack and we were initially "satisfied", but didn't see it get improved that much nor noticed any attempts of it trying to tackle other problems. Then they raised their prices to even higher than Slack's, which we took as a bit of dick move seeing as we were self-hosting it + it has nowhere near the experience of Slack. Push notifications in general didn't seem to be that good. Zulip has a nice spin on the way discussions work with their concept of "topics". It lends itself well to how we conceptualize the discussions across our development teams, without unnecessarily creating many ad-hoc temp channels (something we'd have done on Slack). We're liking it thus far. That being said I do need to check why it's using about 35 gigs of RAM on our server.
- ssivark 5y agoIs this bug another manifestation of the ubiquitous “confused deputy” problem that results from conflating authorization and authentication? (Trying to relate to some recent stuff I’ve read about the importance of “object capabilities”)
- smartbit 5y agoZulip in Docker¶ Zulip has an officially supported, experimental docker image. Please note that Zulip’s normal installer has been extremely reliable for years, whereas the Docker image is new and has rough edges, so we recommend the normal installer unless you have a specific reason to prefer Docker. [0] A server application without Helm charts? Stateful apps without Kubernetes Operator? For someone living with k8s all day, it feels so strange to need to make a VM, update it, then follow the installation steps and then for years coming having to keep them updated, migrate to new hosts, etc, etc. [0] https://zulip.readthedocs.io/en/stable/production/deployment.html#zulip-in-docker https://zulip.readthedocs.io/en/stable/production/deployment...
- deleted 5y ago[deleted]
- northrup 5y agoI couldn't agree more. I'm unsure why it appears that docker is a such an afterthought.
- quadrifoliate 5y agoI see it as "this is the official way that the project uses to host, and they have been kind enough to share it with you". I don't think Zulip themselves use Helm charts or Kubernetes Operators to host their instances. If you think hosting an instance without these is such a pain, why not just pay them to manage it for you? At least you got the option to self-host, which is not something you'll ever get with Slack.
- tabbott 5y agoNo team is capable of writing complex software without eventually introducing security bugs, and we (Zulip) are no exception. I'm disappointed that we introduced this bug, and would like to apologize to our users. As a bit of commentary, my experience is that most SaaS vendors fix security bugs quietly. Others will do an brief internal investigation and only consider doing a public disclosure if they believe data privacy regulations require them to do so, because they discovered that the vulnerability had been in fact exploited. Usually public disclosure decisions are made by business executives with PR considerations in mind, so that shouldn't be surprising. See, for example, https://www.zdnet.com/article/slack-resets-passwords-for-1-of-its-users-because-of-2015-hack/ https://www.zdnet.com/article/slack-resets-passwords-for-1-o.... Zulip's core values include transparency, and our policy is to publicly disclose all security bugs that we discover with a formal CVE number, and this blog post is part of that practice. As noted in the blog post, we did an extensive audit and emailed every customer who our audit logs could not prove was not affected with enough detail to let them audit the situation. We did that despite our audit finding no evidence that this vulnerability was ever intentionally exploited, because we think it's the right thing to do. Some technical detail I can add for those interested is that our postmortem plans following this incident include further investment in the internal audit log system used for the investigation (`RealmAuditLog`, if any readers feel like grepping our codebase). Improvements we made in mid-2020 were very helpful in investigating whether this bug had in fact been exploited, and we take this as a sign that we should increase investment in that system.
- tabbott 5y agoAs a side note, I'm surprised that this specific security disclosure ended up on the Hacker News homepage, while our security release about an RCE issue affecting self-hosted Zulip servers last month did not (https://blog.zulip.com/2022/01/25/zulip-server-4-9-security-release/ https://blog.zulip.com/2022/01/25/zulip-server-4-9-security-...). The core bug there an insecure secret generation algorithm in upstream Erlang/RabbitMQ, which seems more broadly notable to me! Despite our spending many hours composing detailed reports and lobbying security teams to get this problem fixed for everyone, not just Zulip, `apt install rabbitmq-server` continues to make a Debian/Ubuntu system vulnerable to RCE, and this fact has apparently been public for years. We did manage to get `rabbitmq-server` fixed in Debian testing, and it is scheduled to be included in the next Debian stable release, I would really have thought an RCE issue like this would result in an immediate security advisory. As a final remark, if you self-host Zulip, please subscribe to our announcements mailing list (https://groups.google.com/g/zulip-announce https://groups.google.com/g/zulip-announce) and make sure your installation is up to date, so that you benefit from the hard work our security team does to keep Zulip users safe.
- roamerz 5y agoWe use Zulip at work with about 70 daily active users. We evaluated other popular competitors both open source and paid. Zulip came out on top because it was spot on with our use case and integrated easily with our infrastructure. Since we rolled it out (about a year ago) it has been the most stable application in our environment- it is rock solid. Thank you Zulip Team for all of your hard and excellent work.