CVE-2022-36453
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 API of Mitel MiCollab 9.1.3 through 9.5.0.101 could allow an authenticated attacker to modify their profile parameters due to improper authorization controls. A successful exploit could allow the authenticated attacker to control another extension number.
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 · high confidenceThis is an authorization bypass in Mitel MiCollab Client API where authenticated users can modify profile parameters to take control of arbitrary extension numbers, likely due to missing or insufficient ownership/permission checks on profile update operations.
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.1.3, <= 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 MiCollab installation versionAccess the MiCollab administration interface or check the installed software package version through the system management console or command line tools used by your deployment methodAffected if The installed version falls within the range >= 9.1.3 and <= 9.5.0.101
-
Verify MiCollab Client API is exposedConfirm that the MiCollab Client API service is running and accessible to end users. Check the API endpoint configuration in the MiCollab administration panel or system services listAffected if The MiCollab Client API is enabled and accessible to authenticated users in your environment
-
Review API access logs for profile modification endpointsLocate the MiCollab API access logs (typically found in the service logs directory or via the administration interface log viewer). Search for POST/PUT requests to profile update endpoints, looking for the 'extension' or 'profile' parameter in the request bodyAffected if Logs show profile modification requests that reference extension numbers not belonging to the authenticated user making the request
-
Inspect user profile associationsQuery the user directory or database to verify that each user account is properly associated with only their assigned extension number. Look for any anomalies where users have profile records referencing multiple or unauthorized extensionsAffected if User profiles exist with extensions that do not match the user's assigned extension or show unexpected cross-associations
Your environment is affected if MiCollab version is between 9.1.3 and 9.5.0.101 inclusive AND the Client API is accessible to authenticated users, particularly if log analysis reveals profile modifications to unauthorized extensions.
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 dataApply vendor security update beyond version 9.5.0.101. Until then, monitor API access logs for unauthorized profile modifications and consider rate-limiting or additional validation on profile parameter endpoints.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36453 — 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-36453 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