# CVE-2020-11878: Hardcoded credentials in n/a

> The Jitsi Meet Docker stack uses default passwords for system accounts, allowing attackers to gain unauthorized access and escalate privileges.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mf23-9v58-x7jv

## What is CVE-2020-11878?

CVE-2020-11878 is a critical vulnerability in n/a, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Jitsi Meet (aka docker-jitsi-meet) stack on Docker before stable-4384-1 uses default passwords (such as passw0rd) for system accounts.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2020-11878?

It affects 1 product.


Products: Jitsi Meet.

## How do I fix CVE-2020-11878?

No fix has been published for CVE-2020-11878 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-11878 being exploited?

There is no known exploitation of CVE-2020-11878 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2021-26812](https://insights.sbomify.com/CVE-2021-26812/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11878 and fix it if it is affected.

What it is: CVE-2020-11878 is a critical vulnerability in n/a, published on 17 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-11878 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-11878/ (Markdown: https://insights.sbomify.com/CVE-2020-11878/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-11878
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-11878
- OSV: https://osv.dev/vulnerability/CVE-2020-11878

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-11878/
Summaries are generated and may contain mistakes; the official description above is the record.