Prime Lan Management SolutionApplication · Cisco

CVE-2017-12225

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

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
A vulnerability in the web functionality of the Cisco Prime LAN Management Solution could allow an authenticated, remote attacker to hijack another user's administrative session, aka a Session Fixation Vulnerability. The vulnerability is due to the reuse of a preauthentication session token as part of the postauthentication session. An attacker could exploit this vulnerability by obtaining the presession token ID. An exploit could allow an attacker to hijack an existing user's session. Known Affected Releases 4.2(5). Cisco Bug IDs: CSCvf58392.

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

This is a session fixation vulnerability in Cisco Prime LAN Management Solution where the pre-authentication session token is reused as the post-authentication session token. An attacker who obtains the pre-session token ID can continue using it after the user authenticates, effectively hijacking the user's administrative session.

MitigationApply the Cisco fix for bug CSCvf58392 or upgrade to a patched release. As a compensating control, ensure users close all sessions after authentication and avoid accessing LMS from shared/untrusted systems.

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.2\(5\)

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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. Confirm Cisco Prime LMS installation
    Identify if Cisco Prime LAN Management Solution is deployed in your environment. This is typically installed on Linux or Solaris systems and accessed via web interface on ports 8080 or 8443.
    Affected if You cannot confirm the product is installed - you are not affected by this CVE.
  2. Determine installed version
    Access the LMS web interface and navigate to the About or Version page, or check via CLI using 'show version' or inspect the installed RPM/package: 'rpm -q cisco-prime-lms' or check /opt/CSCOlms/etc/lms.ini for version string.
    Affected if The installed version is NOT exactly 4.2(5) - you are not affected by this specific CVE.
  3. Verify session token behavior (optional confirmation)
    If running version 4.2(5), capture a session token before authentication, authenticate with valid credentials, then check if the post-authentication session ID matches the pre-authentication token. Compare cookie or session identifier before and after login.
    Affected if The session token remains identical before and after authentication - you are confirmed affected by CVE-2017-12225.

You are affected by CVE-2017-12225 ONLY if your installed Cisco Prime LAN Management Solution is exactly version 4.2(5) and the pre-authentication session token is reused as the post-authentication session token.

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

Apply the Cisco fix for bug CSCvf58392 or upgrade to a patched release. As a compensating control, ensure users close all sessions after authentication and avoid accessing LMS from shared/untrusted systems.

Fix this in Prime Lan Management Solution Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-12225 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-12225 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