# CVE-2020-9379: Information disclosure in n/a

> Authenticated users can access sensitive user conversation data in MiContact Center Business, requiring a patch to prevent unauthorized disclosure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-vg66-2m2c-p54v

## What is CVE-2020-9379?

CVE-2020-9379 is a medium-severity vulnerability in n/a, published on 25 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Software Development Kit of the MiContact Center Business with Site Based Security 8.0 through 9.0.1.0 before KB496276 allows an authenticated user to access sensitive information. A successful exploit could allow unauthorized access to user conversations.

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

It affects 1 product.


Products: Mitel Micontact Center Business.

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

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

## Is CVE-2020-9379 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-22854](https://insights.sbomify.com/CVE-2023-22854/): Path traversal in n/a (critical 9.1)
- [CVE-2021-3352](https://insights.sbomify.com/CVE-2021-3352/): Missing authorization in n/a (critical 9.1)
- [CVE-2024-42514](https://insights.sbomify.com/CVE-2024-42514/): Missing authorization in n/a (high 8.1)
- [CVE-2024-28069](https://insights.sbomify.com/CVE-2024-28069/): Information disclosure in n/a (high 7.5)
- [CVE-2020-24692](https://insights.sbomify.com/CVE-2020-24692/): Cross-site scripting in n/a (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9379 is a medium-severity vulnerability in n/a, published on 25 Feb 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9379 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-9379/ (Markdown: https://insights.sbomify.com/CVE-2020-9379/index.md)
```

## Sources

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

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