dbcve.org
CryptocatApplication · Cryptocat Project

CVE-2013-2260

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-04
Fix available
A fix is available. Upgrade to 2.0.22 or later.
See remediation →
100/100
Remediation priority · Urgent
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: Cryptocat.random() Function Array Key has Entropy Weakness

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's random() function used a flawed method to generate random array keys with insufficient entropy, making the generated values predictable. This undermines the cryptographic protections of the messaging application by allowing attackers to potentially brute-force or deduce the random values used in encryption operations.

MitigationUpgrade to Cryptocat version 2.0.22 or later which implements proper cryptographic random number generation with adequate entropy sources.

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
High
Availability
High

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

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. Locate the Cryptocat version
    Identify the installed Cryptocat version - for browser extensions, check the extension details in browser settings; for web deployments, check the application UI (typically in About/Help section) or view the main JavaScript file metadata
    Affected if Version displayed is less than 2.0.22 or version information cannot be determined (indicating an older release)
  2. Verify the random function implementation
    Examine the Cryptocat JavaScript source code for the random() function implementation - look for methods generating random array keys used in encryption operations
    Affected if The random() function uses a predictable algorithm without proper entropy sources (code inspection would show insufficient randomness generation)

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 2.0.22 or later
Fixed in 2.0.22
Interim mitigation

Upgrade to Cryptocat version 2.0.22 or later which implements proper cryptographic random number generation with adequate entropy sources.

Recommended fix High confidence

2.0.22

  1. Upgrade Cryptocat to version 2.0.22 or later to resolve the insufficient entropy weakness in the random() function array key generation

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

Fix this in Cryptocat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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