# CVE-2020-29042: Security feature bypass in n/a

> Attackers can bypass meeting access codes via brute-force attacks due to unlimited entry attempts in BigBlueButton.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7q2f-66h6-82pj

## What is CVE-2020-29042?

CVE-2020-29042 is a low-severity vulnerability in n/a, published on 26 Nov 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in BigBlueButton through 2.2.29. A brute-force attack may occur because an unlimited number of codes can be entered for a meeting that is protected by an access code.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 1 product.


Products: Bigbluebutton Bigbluebutton.

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

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

## Is CVE-2020-29042 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-27602](https://insights.sbomify.com/CVE-2020-27602/): Other in n/a (critical 9.8)
- [CVE-2020-27605](https://insights.sbomify.com/CVE-2020-27605/): Code injection in n/a (critical 9.8)
- [CVE-2020-12443](https://insights.sbomify.com/CVE-2020-12443/): Path traversal in n/a (critical 9.8)
- [CVE-2020-27613](https://insights.sbomify.com/CVE-2020-27613/): Hardcoded credentials in n/a (high 8.4)
- [CVE-2021-4143](https://insights.sbomify.com/CVE-2021-4143/): Cross-site Scripting (XSS) - Generic in bigbluebutton/bigbluebutton (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-29042 is a low-severity vulnerability in n/a, published on 26 Nov 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-29042 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-29042/ (Markdown: https://insights.sbomify.com/CVE-2020-29042/index.md)
```

## Sources

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

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