# CVE-2022-36451: Server-side request forgery in n/a

> An authenticated attacker can perform Server-Side Request Forgery in MiCollab Client server to access internal resources via the host server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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 Oct 2022
- **Updated:** 7 May 2025
- **Also known as:** GHSA-g6v8-pg97-856j

## What is CVE-2022-36451?

CVE-2022-36451 is a high-severity server-side request forgery vulnerability in n/a, published on 25 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability in the MiCollab Client server component of Mitel MiCollab through 9.5.0.101 could allow an authenticated attacker to conduct a Server-Side Request Forgery (SSRF) attack due to insufficient restriction of URL parameters. A successful exploit could allow an attacker to leverage connections and permissions available to the host server.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-36451?

It affects 1 product.


Products: Mitel Micollab.

## How do I fix CVE-2022-36451?

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

## Is CVE-2022-36451 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-26143](https://insights.sbomify.com/CVE-2022-26143/): MiCollab, MiVoice Business Express Access Control (critical 9.8, exploited in the wild)
- [CVE-2024-41713](https://insights.sbomify.com/CVE-2024-41713/): Mitel MiCollab Path Traversal (critical 9.1, exploited in the wild)
- [CVE-2024-55550](https://insights.sbomify.com/CVE-2024-55550/): Mitel MiCollab Path Traversal (medium 4.4, exploited in the wild)
- [CVE-2024-35285](https://insights.sbomify.com/CVE-2024-35285/): Command injection in n/a (critical 9.8)
- [CVE-2024-35286](https://insights.sbomify.com/CVE-2024-35286/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-36451 and fix it if it is affected.

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

## Sources

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

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