Prime InfrastructureApplication · Cisco
CVE-2016-1359
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 · uneditedCisco Prime Infrastructure 3.0 allows remote authenticated users to execute arbitrary code via a crafted HTTP request that is mishandled during viewing of a log file, aka Bug ID CSCuw81494.
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 Infrastructure 3.0 contains a code injection vulnerability where remote authenticated users can execute arbitrary code by sending a crafted HTTP request that is improperly handled during the log file viewing functionality. The vulnerability allows privilege escalation from authenticated user to code execution.
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
= 3.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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cisco Prime Infrastructure is installedCheck if the Cisco Prime Infrastructure web interface is accessible on your network (typically ports 443 or 8080). Identify the host running this service.Affected if Cisco Prime Infrastructure is present in your environment
-
Confirm the installed version is 3.0Access the Cisco Prime Infrastructure web UI and navigate to the version information page (usually under Help > About), or use the CLI command 'show version' on the appliance. Compare the version to the affected version 3.0.Affected if The version is exactly 3.0 (no other versions are affected)
-
Check if web-based log viewing feature is enabledIn the Cisco Prime Infrastructure web UI, locate the log file viewing functionality (typically under Administration > Troubleshooting > Logs or similar path). Verify if this feature is accessible to authenticated users.Affected if The log viewing web feature is accessible to users
-
Determine if remote authenticated access is permittedReview the access control settings for Cisco Prime Infrastructure. Check if remote authentication (local or external such as TACACS+/RADIUS) is configured and allows user login to the web interface.Affected if Remote authenticated user access to the web interface is enabled
Your environment is affected only if Cisco Prime Infrastructure version 3.0 is running with the web-based log viewing feature accessible to remote authenticated users.
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 the relevant Cisco patch for Bug ID CSCuw81494. Until patched, restrict administrative access to trusted users only and monitor for suspicious log file access patterns.
Fix this in Prime Infrastructure
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1359 — 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-2016-1359 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