# CVE-2021-45310: Sangoma Technologies Corporation Switchvox Version 102409 is affected by an information disclosure vulnerability due to an improper access restriction.


- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5jhr-vv8x-5wg9

## What is CVE-2021-45310?

CVE-2021-45310 is a medium-severity vulnerability in n/a, published on 14 Feb 2022. 

### Official description

Sangoma Technologies Corporation Switchvox Version 102409 is affected by an information disclosure vulnerability due to an improper access restriction. Users information such as first name, last name, acount id, server uuid, email address, profile image, number, timestamps, etc can be extracted by sending an unauthenticated HTTP GET request to the https://Switchvox-IP/main?cmd=invalid_browser.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-45310?

It affects 1 product.


Products: Sangoma Switchvox.

## How do I fix CVE-2021-45310?

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

## Is CVE-2021-45310 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-9586](https://insights.sbomify.com/CVE-2026-9586/): Sangoma Switchvox SQL Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-45310 and fix it if it is affected.

What it is: CVE-2021-45310 is a medium-severity vulnerability in n/a, published on 14 Feb 2022. 
Exploitation: There is no known exploitation of CVE-2021-45310 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-2021-45310/ (Markdown: https://insights.sbomify.com/CVE-2021-45310/index.md)
```

## Sources

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

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