dbcve.org
ZulipApplication

CVE-2022-35962

MEDIUM · 5.7 CVSS v3.1 Published 2022-08-29
Fix available
A fix is available. Upgrade to 27.190 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Zulip is an open source team chat and Zulip Mobile is an app for iOS and Andriod users. In Zulip Mobile through version 27.189, a crafted link in a message sent by an authenticated user could lead to credential disclosure if a user follows the link. A patch was released in version 27.190.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Zulip Mobile versions through 27.189 contain a vulnerability where a crafted link embedded in a message from an authenticated user can lead to credential disclosure when a recipient clicks the link. The link appears legitimate but is designed to exfiltrate credentials or session tokens.

MitigationUpgrade Zulip Mobile to version 27.190 or later to obtain the patch that addresses this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ZulipApplication
Affected:< 27.190

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Zulip server version
    Log into the Zulip server admin interface and navigate to the 'Server settings' or 'Versions' page, or use the API endpoint /api/v1/server_settings to retrieve the server version
    Affected if The reported version is below 27.190
  2. Verify mobile app access is enabled
    In the Zulip admin console under 'Mobile' or 'Mobile apps' settings, check whether mobile app access and push notifications are permitted for users
    Affected if Mobile app access is enabled and the server version is below 27.190
  3. Check message link preview settings
    Navigate to the Zulip server admin settings under 'Linkifier' or 'Message content' settings and inspect whether link previews are automatically generated for message links
    Affected if Link previews are enabled and the server version is below 27.190
  4. Review authentication methods in use
    In the admin console under 'Authentication methods', list all enabled authentication backends (LDAP, SAML, password, etc.) to understand what credentials could be targeted
    Affected if Any authentication method is enabled and the server version is below 27.190

A Zulip server running version below 27.190 with mobile app access enabled is vulnerable to credential disclosure via crafted links in messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 27.190 or later
Fixed in 27.190
Interim mitigation

Upgrade Zulip Mobile to version 27.190 or later to obtain the patch that addresses this vulnerability.

Recommended fix High confidence

Zulip Mobile 27.190 or later

  1. 1. Identify the current version of Zulip Mobile installed on iOS or Android devices
  2. 2. For iOS devices: Open the App Store, search for Zulip Mobile, and update to version 27.190 or later
  3. 3. For Android devices: Open the Google Play Store, search for Zulip Mobile, and update to version 27.190 or later
  4. 4. Alternatively, for enterprise deployment, download Zulip Mobile version 27.190 or later from the official Zulip website or enterprise distribution channel
  5. 5. Verify the updated version number after installation to confirm the patch was applied

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Zulip Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-35962 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-35962 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data