dbcve.org
CryptocatApplication · Cryptocat Project

CVE-2013-4104

HIGH · 7.5 CVSS v3.1 Published 2019-11-04
Fix available
A fix is available. Upgrade to 2.0.22 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Cryptocat before 2.0.22 has weak encryption in the Socialist Millionnaire Protocol

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 · moderate confidence

Cryptocat before version 2.0.22 implements the Socialist Millionaire Protocol (SMP) for key exchange and authentication with weak cryptographic primitives, allowing an attacker to potentially compromise the authentication mechanism and impersonate users or decrypt communications.

MitigationUpgrade Cryptocat to version 2.0.22 or later which contains the corrected cryptographic implementation of the Socialist Millionaire Protocol.

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
CryptocatApplication
Affected:< 2.0.22

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify if Cryptocat is installed
    Locate the Cryptocat application in your system (browser extension, desktop app, or mobile app depending on your deployment)
    Affected if Cryptocat is present on the system
  2. Determine the installed Cryptocat version
    Access the application settings, about page, or version information within the Cryptocat installation to find the exact version number
    Affected if The version number cannot be determined or is not visible
  3. Compare installed version to affected range
    Compare your identified version against the affected range: any version before 2.0.22 is vulnerable
    Affected if The installed version is lower than 2.0.22 (e.g., 2.0.21, 2.0.20, etc.)
  4. Verify SMP protocol usage
    Check whether the Socialist Millionaire Protocol (SMP) feature for key exchange or authentication has been used or configured in conversations
    Affected if SMP-based authentication has been used to verify contacts or establish secure sessions

You are affected if Cryptocat version is below 2.0.22 and the SMP protocol was used for authentication or key exchange.

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.

From vendor data
Upgrade available Upgrade to 2.0.22 or later
Fixed in 2.0.22
Interim mitigation

Upgrade Cryptocat to version 2.0.22 or later which contains the corrected cryptographic implementation of the Socialist Millionaire Protocol.

Fix this in Cryptocat Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
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,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4104 — 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-2013-4104 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