dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2016-1358

MEDIUM · 6.4 CVSS v3.0 Published 2016-03-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Cisco Prime Infrastructure 2.2, 3.0, and 3.1(0.0) allows remote authenticated users to read arbitrary files or cause a denial of service via an XML document containing an external entity declaration in conjunction with an entity reference, related to an XML External Entity (XXE) issue, aka Bug ID CSCuw81497.

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 confidence

Cisco Prime Infrastructure versions 2.2, 3.0, and 3.1(0.0) contains an XML External Entity (XXE) injection vulnerability. An authenticated remote attacker can send specially crafted XML documents containing external entity declarations and entity references to read arbitrary files from the server filesystem or cause a denial of service condition.

MitigationUpgrade to a Cisco Prime Infrastructure version that addresses CSCuw81497. If no upgrade is immediately available, disable XML external entity processing in the application's XML parser configuration and restrict authenticated access to minimize attack surface.

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 InfrastructureApplication
Affected:= 2.2= 3.0= 3.1

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
High
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Cisco Prime Infrastructure is installed
    Access the web management interface by navigating to the server's hostname or IP address over HTTPS/HTTP, or check for the product via CLI login if you have server access
    Affected if The Cisco Prime Infrastructure web interface or CLI is accessible, indicating the product is installed
  2. Confirm the installed version matches affected releases
    Log into the Cisco Prime Infrastructure web interface and navigate to the version information page (typically under Administration > Software Updates or Help > About), or use the CLI command 'show version' after SSH login
    Affected if The version displayed is exactly 2.2, 3.0, or 3.1(0.0)
  3. Determine if authenticated access to XML interfaces is possible
    Verify that user accounts with access to XML submission features exist and are active. Check if the XML API or administrative XML submission endpoints are reachable (typically under /webacs/ or similar XML-handling endpoints)
    Affected if Authenticated user accounts can access XML submission features, meaning an attacker with valid credentials could exploit the XXE vulnerability
  4. Check if XML external entity processing is enabled in the parser
    This requires access to application configuration files or XML parser settings. If you have administrative access, review the XML parser configuration for external entity processing settings
    Affected if External entity processing is enabled in the XML parser configuration (this would indicate the vulnerability is present and exploitable)

You are affected if Cisco Prime Infrastructure versions 2.2, 3.0, or 3.1(0.0) are installed and XML interfaces are accessible to authenticated users with external entity processing enabled in the parser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a Cisco Prime Infrastructure version that addresses CSCuw81497. If no upgrade is immediately available, disable XML external entity processing in the application's XML parser configuration and restrict authenticated access to minimize attack surface.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1358 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1358 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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