CVE-2020-9379
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 of the MiContact Center Business with Site Based Security 8.0 through 9.0.1.0 before KB496276 allows an authenticated user to access sensitive information. A successful exploit could allow unauthorized access to user conversations.
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 confidenceThe MiContact Center Business SDK versions 8.0 through 9.0.1.0 contains an information disclosure vulnerability where authenticated users can access sensitive data beyond their authorized scope, specifically user conversation data. This appears to be an authorization bypass in the SDK's handling of user data access requests.
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, <= 9.0.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
- 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 installed MiContact Center Business versionAccess the system administration interface or check the installed software packages for MiContact Center Business. Look for the version number in the product information or about section.Affected if The installed version falls within the range >= 8.0 and <= 9.0.1.0
-
Verify Business SDK component is presentCheck if the MiContact Center Business SDK (Software Development Kit) component is installed and enabled on the system. This is typically found in the product components list or installed modules.Affected if The Business SDK version matches the affected version range (8.0 through 9.0.1.0)
-
Review user access control configurationsExamine the SDK's authorization configuration files and user access permission settings. Specifically look for settings related to user conversation data access and cross-user data retrieval permissions.Affected if The SDK allows authenticated users to query or retrieve conversation data belonging to other users without proper authorization checks
-
Audit access logs for unauthorized conversation data accessReview the MiContact Center Business audit logs or access logs for any instances where users accessed conversation data outside their authorized scope. Look for anomalous data access patterns.Affected if Logs show users accessing conversation records that fall outside their defined authorization boundaries
-
Test cross-user data retrieval capabilityIf you have a test environment, attempt to access conversation data of another user account using an authenticated session with limited permissions to verify if the authorization bypass is present.Affected if A user with limited permissions can successfully retrieve conversation data belonging to other users
Your environment is affected if MiContact Center Business version 8.0 through 9.0.1.0 is installed AND the Business SDK component handles user data access requests without proper authorization enforcement.
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 KB496276 or upgrade to a patched version of MiContact Center Business to fix the authorization flaw in the SDK.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9379 — 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-2020-9379 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