Prime Service CatalogApplication · Cisco
CVE-2022-20680
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 web-based management interface of Cisco Prime Service Catalog could allow an authenticated, remote attacker to access sensitive information on an affected device. This vulnerability is due to improper enforcement of Administrator privilege levels for low-value sensitive data. An attacker with read-only Administrator access to the web-based management interface could exploit this vulnerability by sending a malicious HTTP request to the page that contains the sensitive data. A successful exploit could allow the attacker to collect sensitive information about users of the system and orders that have been placed using the application.
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 Prime Service Catalog's web-based management interface improperly enforces Administrator privilege levels, allowing authenticated read-only Administrators to access sensitive user and order information via malicious HTTP requests to specific pages.
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
Prime Service CatalogApplication
<= 12.0= 12.1CVSS 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 Prime Service Catalog versionAccess the admin console or check the product's 'About' page in the web interface. Alternatively, check the installation directory for version files or run: cd /opt/cuic/ && cat version.properties (or the equivalent path on your system).Affected if The installed version is 12.0 or lower, or exactly version 12.1.
-
Confirm web-based management interface is accessibleVerify the web interface is exposed and reachable at the typical paths: /cueservicemanager/ or /cpe/ . Check network listeners or firewall rules to determine if the management interface is network-accessible.Affected if The web management interface is enabled and accessible over the network.
-
Review Administrator account roles and permissionsLog into the web interface with Administrator credentials. Navigate to User Management or Administration > Users. Identify accounts with 'Read-Only Administrator' or similar limited-admin role types.Affected if One or more read-only Administrator accounts exist in the system.
-
Inspect access logs for unauthorized data accessLocate and review the web server access logs (typically in /opt/cuic/logs/ or similar logs directory). Search for requests from read-only admin accounts to pages such as user list, order details, or sensitive data endpoints.Affected if Logs show HTTP requests from read-only Administrator accounts to pages containing user information or order data that should be restricted.
-
Audit permission boundaries for read-only adminsAs a read-only Administrator, attempt to access pages that should require full Administrator privileges. Compare the allowed endpoints against documented permissions for the read-only role.Affected if Read-only Administrator accounts can retrieve user records, order information, or other sensitive data that should be privileged content.
You are affected if Cisco Prime Service Catalog version 12.0 or lower (or exactly 12.1) is installed, the web management interface is accessible, and read-only Administrator accounts exist that can access privileged user or order information.
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 · scopedApply the Cisco patch when available; until then, restrict network access to the management interface and audit user permissions.
12.1.1 or later
- Ensure you have a complete backup of the Cisco Prime Service Catalog database and configuration
- Review Cisco Prime Service Catalog 12.1.1 release notes for any pre-upgrade requirements
- Download Cisco Prime Service Catalog version 12.1.1 or later from Cisco.com
- Stop all Prime Service Catalog services before upgrading
- Run the upgrade installer following Cisco's documented upgrade procedure
- Verify the upgrade completed successfully by checking the system version
- Log in to the web-based management interface and confirm the vulnerability is addressed by verifying that read-only Administrator accounts can no longer access sensitive user and order information
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Prime Service Catalog
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20680 — 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-20680 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