dbcve.org
Prime Lan Management SolutionApplication · Cisco

CVE-2016-1360

HIGH · 7.1 CVSS v3.0 Published 2016-03-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
Zero-click

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 LAN Management Solution (LMS) through 4.2.5 uses the same database decryption key across different customers' installations, which allows local users to obtain cleartext data by leveraging console connectivity, aka Bug ID CSCuw85390.

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 confidence

Cisco Prime LMS through version 4.2.5 uses a static, identical database decryption key across all customer installations rather than generating unique keys per deployment. This hardcoded key allows any local user with console access to decrypt and read sensitive data stored in the LMS database.

MitigationRestrict console access to authorized personnel only and contact Cisco for patched versions or specific guidance; consider upgrading to a newer LMS version if available. After addressing, rotate any credentials that may have been exposed.

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 Lan Management SolutionApplication
Affected:= 4.1_base= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.2.5= 4.2_base

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

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify the installed Cisco Prime LMS version
    Run 'show version' or check the LMS installation directory for version information. Common locations include /opt/CSCOlms or the LMS installation path. Look for version files or use 'rpm -q cisco-lms' or 'ls -la' in the installation directory.
    Affected if The installed version is 4.1_base, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.2.5, or 4.2_base.
  2. Locate database encryption configuration files
    Search for configuration files related to database encryption in the LMS installation directory. Look for files named 'encryption.properties', 'dbEncryption.properties', or similar files containing 'key', 'encryption', or 'decrypt' in their names using: find /opt/CSCOlms -type f -name '*encry*' 2>/dev/null
    Affected if Encryption configuration files exist and contain hardcoded key values rather than dynamically generated keys.
  3. Inspect the decryption key configuration
    Examine any found encryption configuration files. Look for static, hardcoded key values or credential strings that appear identical across installations. Check for patterns like 'dbKey=', 'decryptionKey=', or similar parameters.
    Affected if The configuration contains a static key value that is identical across different installations rather than a unique per-deployment key.
  4. Verify console access controls
    Review system access controls and user accounts with console or shell access to the LMS server. Check /etc/passwd, /etc/shadow permissions, and sudo configuration for the LMS system account.
    Affected if Multiple unauthorized or non-administrative users have console or shell access to the LMS server.

You are affected if you are running any Cisco Prime LMS version from 4.1_base through 4.2.5 and your installation contains the static hardcoded decryption key in configuration files accessible to local users.

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

Restrict console access to authorized personnel only and contact Cisco for patched versions or specific guidance; consider upgrading to a newer LMS version if available. After addressing, rotate any credentials that may have been exposed.

Fix this in Prime Lan Management Solution Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1360 — 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-1360 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