# CVE-2020-12112: BigBlueButton before 2.2.5 allows remote attackers to obtain sensitive files via Local File Inclusion.


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 23 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wvwr-5mqr-9r9p

## What is CVE-2020-12112?

CVE-2020-12112 is a high-severity vulnerability in n/a, published on 23 Apr 2020. 

### Official description

BigBlueButton before 2.2.5 allows remote attackers to obtain sensitive files via Local File Inclusion.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Bigbluebutton Bigbluebutton.

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

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

## Is CVE-2020-12112 being exploited?

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

Public exploit code:

- BigBlueButton versions lower than 2.2.4 have a LFI vulnerability allowing access to sensitive files. 🚨 (github_poc): https://github.com/tchenu/CVE-2020-12112

## 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-12112 and fix it if it is affected.

What it is: CVE-2020-12112 is a high-severity vulnerability in n/a, published on 23 Apr 2020. 
Exploitation: There is no known exploitation of CVE-2020-12112 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-12112/ (Markdown: https://insights.sbomify.com/CVE-2020-12112/index.md)
```

## Sources

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

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