dbcve.org
Application Networking ManagerApplication · Cisco

CVE-2013-1196

MEDIUM · 6.8 CVSS v2.0 Published 2013-04-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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
The command-line interface in Cisco Secure Access Control System (ACS), Identity Services Engine Software, Context Directory Agent, Application Networking Manager (ANM), Prime Network Control System, Prime LAN Management Solution (LMS), Prime Collaboration, Unified Provisioning Manager, Network Services Manager, Prime Data Center Network Manager (DCNM), and Quad does not properly validate input, which allows local users to obtain root privileges via unspecified vectors, aka Bug IDs CSCug29384, CSCug13866, CSCug29400, CSCug29406, CSCug29411, CSCug29413, CSCug29416, CSCug29418, CSCug29422, CSCug29425, and CSCug29426, a different issue than CVE-2013-1125.

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

Multiple Cisco products contain a CLI input validation flaw that allows local authenticated users to escalate privileges to root. The vulnerability stems from improper validation of user-supplied input in command-line interfaces across ACS, ISE, CDA, ANM, PNCS, LMS, Prime Collaboration, UPM, NSM, DCNM, and Quad. Local access is required for exploitation.

MitigationApply Cisco security patches corresponding to the listed bug IDs. For systems where patches are unavailable, restrict local access to trusted administrators and monitor for unauthorized privilege escalation.

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
Application Networking ManagerApplication
Affected:all versions
Context Directory AgentApplication
Affected:all versions
Identity Services Engine SoftwareApplication
Affected:all versions
Network Services ManagerApplication
Affected:all versions
Prime CollaborationApplication
Affected:all versions
Prime Data Center Network ManagerApplication
Affected:all versions
Prime Lan Management SolutionApplication
Affected:all versions
Prime Network Control SystemApplication
Affected:all versions

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

AV:L/AC:L/Au:S/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 installed Cisco product
    Run 'show version' or 'show system information' at the CLI prompt, or check the product name via the web interface or installed packages on the system. Identify if the product matches any of these: Cisco Application Networking Manager, Cisco Context Directory Agent, Cisco Identity Services Engine Software, Cisco Network Services Manager, Cisco Prime Collaboration, Cisco Prime Data Center Network Manager, Cisco Prime Lan Management Solution, or Cisco Prime Network Control System.
    Affected if The installed product is one of the listed Cisco products. If your product matches any of these, all versions are considered affected.
  2. Verify local CLI access is available
    Confirm that CLI access is enabled on the system. Check whether local login credentials can be used to access the command-line interface via console, SSH, or telnet. Review system access configurations in /etc/passwd, /etc/ssh/sshd_config, or the product-specific access control settings.
    Affected if Local authenticated CLI access is available. The vulnerability requires local access, so if CLI access is completely disabled and the system is not network-accessible, the exploit surface is reduced.
  3. Check for unauthorized administrator accounts
    Review local user accounts on the system using 'show user' or 'show running-config' commands within the product CLI, or examine /etc/shadow and /etc/group for unexpected accounts with root or administrator privileges. Compare against known-good baseline of authorized administrators.
    Affected if Unexpected accounts with elevated privileges exist. This may indicate the vulnerability has been exploited.
  4. Review recent privilege escalation events
    Examine system logs for authentication events followed by privilege changes. Check /var/log/secure, /var/log/messages, or product-specific logs for commands executed after user login that indicate privilege escalation attempts.
    Affected if Logs show authenticated users executing commands or accessing resources beyond their assigned privilege level.

You are affected if any of the listed Cisco products (ANM, CDA, ISE, NSM, Prime Collaboration, PNCS, LMS, DCNM) are installed and local CLI access is available, as all versions of these products contain the input validation flaw.

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 Cisco security patches corresponding to the listed bug IDs. For systems where patches are unavailable, restrict local access to trusted administrators and monitor for unauthorized privilege escalation.

Fix this in Application Networking Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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