CVE-2021-3352
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 · uneditedThe Software Development Kit in Mitel MiContact Center Business from 8.0.0.0 through 8.1.4.1 and 9.0.0.0 through 9.3.1.0 could allow an unauthenticated attacker to access (view and modify) user data without authorization due to improper handling of tokens.
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 confidenceThe Mitel MiContact Center Business SDK has an authentication bypass vulnerability in versions 8.0.0.0-8.1.4.1 and 9.0.0.0-9.3.1.0 due to improper token handling. An unauthenticated remote attacker can exploit this to view and modify user data without authorization, achieving a CVSS 9.1 critical severity rating.
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>= 8.0.0.0, <= 8.1.4.1>= 9.0.0.0, <= 9.3.1.0CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 MiContact Center Business SDK installationSearch for Mitel MiContact Center Business installation directories on the server. Check common paths such as C:\Program Files\Mitel\ or /opt/mitel/ for the application. Look for SDK documentation or license files that reference the product version.Affected if The software is found installed on the system
-
Determine the installed versionLocate the version information in the installation directory. Check for version.txt, about dialog, or the application executable properties. The version format follows 8.x.x.x or 9.x.x.x.Affected if The installed version falls within 8.0.0.0-8.1.4.1 or 9.0.0.0-9.3.1.0
-
Identify exposed SDK endpointsReview web server configuration files (IIS, Apache, or built-in web server configs) for exposed API endpoints. Look for paths related to the SDK such as /api/, /services/, or /sdk/ endpoints accessible over HTTP/HTTPS.Affected if SDK API endpoints are accessible from the network without proper authentication barriers
-
Verify authentication enforcement on endpointsSend unauthenticated HTTP requests to the identified SDK endpoints using curl or a browser. Observe whether the API returns data without requiring valid authentication tokens or session cookies.Affected if Unauthenticated requests to SDK endpoints return successful responses with user data instead of 401/403 errors
A system is affected if MiContact Center Business SDK versions 8.0.0.0-8.1.4.1 or 9.0.0.0-9.3.1.0 are installed AND the SDK API endpoints are network-accessible without authentication being enforced.
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-supplied patches to update the SDK to a version beyond 8.1.4.1 or 9.3.1.0, or upgrade to a fixed release. If patches are unavailable, consider network segmentation and API gateway controls to restrict unauthorized access to affected SDK endpoints.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-3352 — 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-2021-3352 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