CVE-2023-20061
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 · uneditedMultiple vulnerabilities in Cisco Unified Intelligence Center could allow an authenticated, remote attacker to collect sensitive information or perform a server-side request forgery (SSRF) attack on an affected system. Cisco plans to release software updates that address these vulnerabilities.
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 confidenceCisco Unified Intelligence Center contains multiple vulnerabilities allowing authenticated remote attackers to collect sensitive information or perform server-side request forgery (SSRF) attacks. The SSRF vulnerability is particularly concerning as it could allow attackers to make the affected server request internal resources, potentially bypassing network segmentation.
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 dataall versionsall versionsall versions< 12.6\(2\)CVSS 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 Cisco contact center productsReview system inventory or run 'show version' on the Cisco device to list installed software packages and determine if Unified Intelligence Center, Packaged Contact Center Enterprise, Unified Contact Center Enterprise, or Unified Contact Center Express are presentAffected if Any of these products are installed and the version of Unified Intelligence Center is below 12.6(2)
-
Check Unified Intelligence Center versionAccess the Unified Intelligence Center admin interface and navigate to Help > About, or use the CLI command 'show version' if available, to confirm the installed software versionAffected if The installed version is below 12.6(2) or the version cannot be determined (all versions below 12.6(2) are affected)
-
Verify web interface exposureReview network firewall rules and access lists to determine if the Unified Intelligence Center web interface (typically ports 443 or 8080) is accessible from untrusted networks or the internetAffected if The web interface is accessible from untrusted networks without VPN or proper network segmentation
-
Confirm user authentication controlsReview user accounts and role-based access control (RBAC) configuration in the Unified Intelligence Center admin panel to verify that only authorized, authenticated users have accessAffected if Anonymous or unauthenticated access is possible, or if default credentials remain in use
-
Check for suspicious outbound requestsReview outbound network traffic logs and web server access logs for the Unified Intelligence Center server, looking for unusual internal IP requests (such as 10.x.x.x, 192.168.x.x, 127.x.x.x) or unexpected API callsAffected if The server has made outbound requests to internal resources that were not initiated by legitimate administrators
A user is affected if they run any of the listed products with Unified Intelligence Center version below 12.6(2) and the web interface is accessible to attackers, particularly from untrusted networks.
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.
dbcve · scoped12.6
Apply the Cisco software update when released through the Cisco support portal. Until then, restrict access to the Unified Intelligence Center to only authenticated, authorized users and monitor for unusual outbound requests.
Unified Intelligence Center: 12.6(2) or later; Other products: No fixed version specified - awaiting Cisco patch release
- 1. Identify the current version of Cisco Unified Intelligence Center in your environment
- 2. For Unified Intelligence Center: Upgrade to version 12.6(2) or later to remediate this vulnerability
- 3. For Packaged Contact Center Enterprise, Unified Contact Center Enterprise, and Unified Contact Center Express: Monitor Cisco security advisories for upcoming patches; no fixed version is currently specified
- 4. After upgrading, verify the installation was successful and the vulnerability is remediated
- 5. Review Cisco Unified Intelligence Center logs and access controls to ensure no unauthorized access occurred
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20061 — 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-2023-20061 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