CVE-2022-36451
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a Server-Side Request Forgery (SSRF) vulnerability in the MiCollab Client server component of Mitel MiCollab (versions through 9.5.0.101). The vulnerability stems from insufficient restriction of URL parameters, allowing an authenticated attacker to manipulate the server into making arbitrary HTTP requests to internal or external resources. This enables the attacker to leverage the server's network position and trusted relationships to access sensitive services or internal systems.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 9.5.0.101CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Mitel MiCollab installationLocate MiCollab installation directories or check system services for MiCollab components. Common paths include /opt/mitel/micollab or C:\Program Files\Mitel\MiCollab on Windows. Use 'ls' or directory listing commands to find MiCollab-related directories.Affected if Mitel MiCollab software is found on the system
-
Determine MiCollab versionCheck the installed version by reviewing version files, About dialogs, or running version lookup commands specific to MiCollab. Common methods include examining README files, version.info files, or using vendor-provided version inquiry tools within the MiCollab installation directory.Affected if The installed version is 9.5.0.101 or lower (any version through 9.5.0.101)
-
Verify MiCollab Client server component statusIdentify if the MiCollab Client server component is running and enabled. Check Windows Services, systemd services, or the MiCollab administration console to determine if the Client server component is active. This component handles URL parameters and is the attack surface for SSRF.Affected if The MiCollab Client server component is running and accessible on the network
-
Check authentication configurationReview MiCollab user authentication settings and determine if unauthenticated access is possible to the Client server component endpoints. Examine authentication configuration files or admin console settings to understand the authentication requirements for URL-based requests.Affected if An attacker can obtain valid credentials or the component accepts authenticated requests from external sources
The environment is affected if Mitel MiCollab version 9.5.0.101 or lower is installed with the MiCollab Client server component enabled and accessible to an authenticated attacker.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based validation for URL parameters and restrict outbound network connections from the MiCollab server. Apply any vendor patches when available and consider network segmentation to limit the server's ability to reach internal resources.
- Consultation4.0 h
- Implementation12.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-36451 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data