Prime Service CatalogApplication · Cisco
CVE-2015-0581
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 XML parser in Cisco Prime Service Catalog before 10.1 allows remote authenticated users to read arbitrary files or cause a denial of service (CPU and memory consumption) via an external entity declaration in conjunction with an entity reference, as demonstrated by reading private keys, related to an XML External Entity (XXE) issue, aka Bug ID CSCup92880.
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 XML parser in Cisco Prime Service Catalog before version 10.1 is vulnerable to XML External Entity (XXE) injection. Authenticated remote users can exploit external entity declarations combined with entity references to read arbitrary files from the server filesystem (including sensitive data like private keys) or cause denial of service through excessive CPU and memory consumption.
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
<= 10.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
- Authentication
- Single
- Confidentiality
- Complete
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:S/C:C/I:N/A:P
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.
-
Determine installed Cisco Prime Service Catalog versionAccess the product's About page or admin interface to view the current version number. Alternatively, check installation logs or the product's version file if accessible through the deployment directory.Affected if The installed version is 10.0 or any earlier version (versions prior to the 10.1 fix release).
-
Identify XML parser configurationLocate configuration files related to XML processing in the application deployment. Look for XML parser, Xerces, or similar XML library configuration files within the product's config directory.Affected if External entity processing is enabled in the XML parser configuration, allowing external entity declarations to be processed.
-
Verify XML input processing is activeDetermine if the application accepts XML input from users through any API, file upload, or data import functionality. Review application features that parse XML documents.Affected if User-supplied or externally-sourced XML documents are being parsed by the application without disabled external entity processing.
A user is affected if Cisco Prime Service Catalog version is 10.0 or earlier and the XML parser processes input with external entity processing enabled.
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 dataUpgrade Cisco Prime Service Catalog to version 10.1 or later to obtain the fix for this XXE vulnerability. Alternatively, disable external entity processing in the XML parser configuration if immediate upgrading is not feasible.
Fix this in Prime Service Catalog
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0581 — 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-2015-0581 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