dbcve.org
CryptocatApplication · Cryptocat Project

CVE-2013-4107

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-05
Fix available
A fix is available. Upgrade to 2.0.22 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.js handlePresence() has cross site scripting

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

Cryptocat before version 2.0.22 contains a cross-site scripting (XSS) vulnerability in the handlePresence() function within cryptocat.js. The function fails to properly sanitize or escape user-supplied input when processing presence data, allowing an attacker to inject malicious JavaScript code that executes in the context of other users' browsers.

MitigationUpgrade Cryptocat to version 2.0.22 or later, which includes proper input validation and output encoding in the handlePresence() function to prevent XSS attacks.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Cryptocat extension is installed
    Open your browser's extension manager - for Chrome go to chrome://extensions, for Firefox go to about:addons - and look for Cryptocat in the list of installed extensions
    Affected if Cryptocat is listed as installed
  2. Identify the installed Cryptocat version
    In the browser extension manager, locate Cryptocat and note the version number displayed for the extension
    Affected if The version number cannot be determined or is not visible
  3. Compare version against vulnerable range
    Compare the installed version number to the affected range: any version before 2.0.22 is vulnerable (for example, 2.0.21, 2.0.20, etc.)
    Affected if The installed version is less than 2.0.22

The user is affected if Cryptocat browser extension is installed and the version is below 2.0.22, since the unpatched handlePresence() function in cryptocat.js will process malicious presence data as executable JavaScript.

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 includes proper input validation and output encoding in the handlePresence() function to prevent XSS attacks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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