CVE-2022-36454
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 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 impersonate another user's name.
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 confidenceMitel MiCollab Client API through 9.5.0.101 contains improper authorization controls allowing authenticated users to modify profile parameters belonging to other users, enabling name impersonation. The vulnerability stems from missing or insufficient authorization validation on profile update API endpoints.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 versionLocate the installed MiCollab version number in the system administration interface or system inventoryAffected if Version is 9.5.0.101 or earlier (any version up to and including 9.5.0.101)
-
Confirm Client API is accessibleVerify that the MiCollab Client API endpoints are exposed and reachable from the network segment where users operateAffected if API is accessible without additional network segmentation or authentication layers beyond what MiCollab provides
-
Review profile update API authorizationExamine the API endpoint configuration for profile update operations to confirm whether authorization validates the requesting user against the target profileAffected if API permits a user to modify profile parameters of other user accounts without proper ownership verification
-
Audit logs for profile modification anomaliesSearch authentication and profile change logs for instances where profile updates were performed on user accounts by different authenticated usersAffected if Logs show profile modifications where the modifying user differs from the profile owner
-
Check for unauthorized name changesCompare recent profile display name changes against legitimate user requests to identify impersonation patternsAffected if Profile display names have been changed to impersonate other users without authorization
User is affected if MiCollab version is 9.5.0.101 or earlier and the Client API is accessible to users who should not be able to modify other users profiles.
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 patch for CVE-2022-36454. Until patch is available, restrict API access to trusted users and monitor for unauthorized profile modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-36454 — 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-36454 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