dbcve.org
Prime Lan Management SolutionApplication · Cisco

CVE-2012-6392

HIGH · 10.0 CVSS v2.0 Published 2013-01-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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) 4.1 through 4.2.2 on Linux does not properly validate authentication and authorization requests in TCP sessions, which allows remote attackers to execute arbitrary commands via a crafted session, aka Bug ID CSCuc79779.

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 LAN Management Solution versions 4.1 through 4.2.2 on Linux contains a critical authentication and authorization validation flaw in its TCP session handling. Attackers can send crafted TCP sessions to bypass authentication and execute arbitrary commands with the privileges of the affected service, achieving remote code execution at CVSS 10 severity.

MitigationImmediately restrict network access to Cisco Prime LMS systems using firewall rules or network segmentation. Apply the vendor patch or upgrade to a version beyond 4.2.2 as specified in Cisco's advisory for bug CSCuc79779.

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= 4.2= 4.2.1= 4.2.2

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 if Cisco Prime LMS is installed
    Look for Cisco Prime LMS installation directories such as /opt/CSCOlms or check for the 'cms' or 'lms' processes running on the system using commands like 'ps aux | grep -i cisco' or 'ls /opt/CSCOlms'
    Affected if The software is found on the system
  2. Determine the installed version
    Check the version file typically found in the LMS installation directory, such as running 'cat /opt/CSCOlms/lms 版本文件' or checking the application's about/version information through the web interface if accessible
    Affected if The version returned matches 4.1, 4.2, 4.2.1, or 4.2.2
  3. Verify the operating system platform
    Run 'uname -a' or check /etc/os-release to confirm the system is Linux, as this vulnerability specifically affects the Linux platform
    Affected if The operating system is Linux and the LMS version falls within the affected range
  4. Confirm the LMS service is running and exposed
    Check if the Cisco LMS service is active and listening on network ports using 'netstat -tlnp | grep -i lms' or 'ss -tlnp | grep -i lms', and determine if the management interface is network-accessible
    Affected if The service is running and accessible over the network on Linux with an affected version

The environment is affected if Cisco Prime LAN Management Solution version 4.1, 4.2, 4.2.1, or 4.2.2 is installed and running on a Linux system with network-accessible LMS services.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to Cisco Prime LMS systems using firewall rules or network segmentation. Apply the vendor patch or upgrade to a version beyond 4.2.2 as specified in Cisco's advisory for bug CSCuc79779.

Recommended fix Moderate confidence

Upgrade to the latest Cisco Prime LAN Management Solution release beyond 4.2.2 (consult Cisco for the specific fixed version)

  1. 1. Check current Cisco Prime LMS version using 'show version' command or via the web interface.
  2. 2. Review Cisco's official security advisory for CVE-2017-6622 (or relevant bug ID CSCuc79779) on tools.cisco.com for available patches or fixed releases.
  3. 3. If patches are unavailable, plan an upgrade to a newer Cisco Prime LMS release that supersedes version 4.2.2.
  4. 4. Before upgrading, back up the current LMS configuration and database.
  5. 5. Schedule a maintenance window for the upgrade process.
  6. 6. Follow Cisco's official upgrade procedure for LMS 4.x to the latest supported version.
  7. 7. After upgrade, verify the fix by testing authentication and session handling.
  8. 8. Confirm the new version is no longer vulnerable to the command injection flaw.
Caveat Upgrading major versions of LMS may require migration procedures; ensure compatibility with dependent systems and review Cisco upgrade guides for configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Prime Lan Management Solution Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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