dbcve.org
MeetApplication · Jitsi

CVE-2020-11878

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Jitsi Meet (aka docker-jitsi-meet) stack on Docker before stable-4384-1 uses default passwords (such as passw0rd) for system accounts.

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

The Jitsi Meet Docker stack (docker-jitsi-meet) before version stable-4384-1 ships with hardcoded default passwords such as 'passw0rd' for system accounts. These weak default credentials can be exploited by attackers to gain unauthorized access to the video conferencing platform, potentially leading to complete system compromise.

MitigationImmediately change all default passwords to strong, unique credentials before deployment, and upgrade the Jitsi Meet Docker installation to stable-4384-1 or later which removes the default credentials.

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
MeetApplication
Affected:< stable-4384-1

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. Identify the installed docker-jitsi-meet version
    Check the docker-jitsi-meet version by reviewing the release tag, git commit, or the version file in your deployment. If using docker, inspect the image tags or check the CHANGELOG file included in the deployment.
    Affected if The version is earlier than stable-4384-1 (e.g., stable-4281, older releases)
  2. Locate environment configuration files
    Find the .env file or environment configuration files used to deploy the Jitsi Meet Docker stack. These files typically contain passwords and authentication settings for the video conferencing components.
    Affected if Default password values like 'passw0rd' or other weak default credentials are present in the configuration files
  3. Inspect account password settings
    Review all configuration files that define passwords for system accounts (such as Jicofo, Videobridge, Prosody, or web authentication). Look for hardcoded password strings.
    Affected if Any system account is configured with the default password 'passw0rd' or other known weak default passwords
  4. Check for unmodified default credentials
    Compare the passwords in your active deployment configuration against known default values shipped with docker-jitsi-meet. Search configuration files for the string 'passw0rd' or other default password patterns.
    Affected if The passwords match the hardcoded defaults shipped with versions prior to stable-4384-1

You are affected if your docker-jitsi-meet version is earlier than stable-4384-1 AND your configuration contains the hardcoded default password 'passw0rd' or other weak default credentials for system accounts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately change all default passwords to strong, unique credentials before deployment, and upgrade the Jitsi Meet Docker installation to stable-4384-1 or later which removes the default credentials.

Recommended fix High confidence

stable-4384-1 or later

  1. Backup your current docker-compose.yml and environment configuration files
  2. Pull the latest Jitsi Meet Docker images (docker-compose pull)
  3. Update your docker-compose.yml to use version stable-4384-1 or later
  4. Ensure all default passwords in your .env file are changed from defaults like 'passw0rd' to unique, strong passwords
  5. Restart the containers with docker-compose down && docker-compose up -d
  6. Verify all services are running correctly with docker-compose ps
Caveat Review custom configuration changes as the upgrade may include configuration file updates

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

Fix this in Meet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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