CVE-2013-4108: Multiple unspecified vulnerabilities in Cryptocat Project Cryptocat 2.0.18 have unknown impact and attack vect

This month

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2013-4108 is a critical-severity flaw (CVSS 9.8) affecting cryptocat. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Multiple unspecified vulnerabilities in Cryptocat Project Cryptocat 2.0.18 have unknown impact and attack vectors.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Published	2019-11-14
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: cryptocat project

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-11-14 20:15 UTCPublished CVE record published
2026-06-16 23:56 UTCUpdated Record last modified

cryptocat project cryptocat DOWNGRADE

Affected: 2.0.18

Fixed in: no fixed release known

Safe to downgrade to: a release before 2.0.18

1. Check installed version

apt-cache policy cryptocat || rpm -q cryptocat || cryptocat --version

2. No fixed release: DOWNGRADE to a release before 2.0.18 (Debian / Ubuntu)

apt-cache madison cryptocat sudo apt install cryptocat=<VERSION_BEFORE_2.0.18> sudo apt-mark hold cryptocat

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list cryptocat sudo dnf downgrade cryptocat-<VERSION_BEFORE_2.0.18> sudo dnf versionlock add cryptocat

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-4108?

cryptocat: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2013-4108 being exploited?

CVE-2013-4108 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-4108 affect?

CVE-2013-4108 affects cryptocat. Severity is critical (CVSS 9.8). Multiple unspecified vulnerabilities in Cryptocat Project Cryptocat 2.0.18 have unknown impact and attack vectors.

How urgent is CVE-2013-4108?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2013-4110 MEDIUM 5.3 MITIGATE Cryptocat has an Unspecified Chat Participant User List Disclosure
CVE-2013-4109 MEDIUM 6.1 DOWNGRADE An unspecified cross-site scripting (XSS) vulnerability exists in Cryptocat Message Handling 1.1.165.
CVE-2013-4107 MEDIUM 6.1 UPGRADE Cryptocat before 2.0.22: cryptocat.js handlePresence() has cross site scripting
CVE-2013-4106 MEDIUM 6.1 UPGRADE A Cross-site scripting (XSS) vulnerability exists in Conversation Overview Nickname in Cryptocat before 2.0.22
CVE-2013-4105 HIGH 7.5 UPGRADE Cryptocat before 2.0.22 has Multiparty Encryption Scheme Information Disclosure

References

← Back to latest CVEs