dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2014-0679

HIGH · 9.0 CVSS v2.0 Published 2014-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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 Infrastructure 1.2 and 1.3 before 1.3.0.20-2, 1.4 before 1.4.0.45-2, and 2.0 before 2.0.0.0.294-2 allows remote authenticated users to execute arbitrary commands with root privileges via an unspecified URL, aka Bug ID CSCum71308.

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 Infrastructure contains an OS command injection vulnerability that allows authenticated remote attackers to execute arbitrary operating system commands with root privileges by leveraging unspecified URLs. The vulnerability stems from insufficient input validation in the web interface.

MitigationApply the vendor-supplied patches for versions 1.2, 1.3, 1.4, and 2.0 as specified in Cisco advisory, or upgrade to the fixed version releases (1.3.0.20-2, 1.4.0.45-2, or 2.0.0.0.294-2 or later).

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
Affected:= 1.2= 1.2.1= 1.3= 1.4= 1.4.1= 2.0

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

AV:N/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 Cisco Prime Infrastructure installation
    Locate the Cisco Prime Infrastructure installation by checking for its web service ports (typically 443, 8443) or by examining installed software directories on the system.
    Affected if The product is installed and running on the target system.
  2. Determine the installed version
    Access the Cisco Prime Infrastructure web interface login page and look for version information, or log into the CLI and use the command 'show version' or check the file /opt/CSMl/etc/version if accessible.
    Affected if The version displayed matches 1.2, 1.2.1, 1.3, 1.4, 1.4.1, or 2.0.
  3. Confirm web interface is accessible
    Attempt to reach the Cisco Prime Infrastructure web interface via HTTPS on the configured port (commonly 443 or 8443) from a network perspective.
    Affected if The web interface is reachable over the network.
  4. Verify authentication is enabled
    Check that the web interface requires authentication by attempting to access protected URLs without credentials and confirming a login prompt is returned.
    Affected if The web interface requires valid credentials for access.

If Cisco Prime Infrastructure is installed and the version is exactly 1.2, 1.2.1, 1.3, 1.4, 1.4.1, or 2.0 with the web interface accessible and authentication enabled, the environment is affected by this CVE.

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

Apply the vendor-supplied patches for versions 1.2, 1.3, 1.4, and 2.0 as specified in Cisco advisory, or upgrade to the fixed version releases (1.3.0.20-2, 1.4.0.45-2, or 2.0.0.0.294-2 or later).

Recommended fix High confidence

Upgrade to minimum fixed version: 1.3.0.20-2 (for 1.2/1.2.1/1.3) or 1.4.0.45-2 (for 1.4) or later

  1. 1. Identify the currently installed Cisco Prime Infrastructure version in the web UI under Administration > Settings > Software Updates or via CLI: show version
  2. 2. Determine the appropriate upgrade path based on current version: if 1.2.x or 1.2.1.x → upgrade to 1.3.0.20-2 or later; if 1.3.x → upgrade to 1.3.0.20-2 or later; if 1.4.x → upgrade to 1.4.0.45-2 or later
  3. 3. Download the upgrade file from Cisco.com Software Center (requires valid service contract)
  4. 4. Back up the current configuration: Administration > Backup & Restore > Backup Now
  5. 5. Schedule a maintenance window as upgrades require downtime
  6. 6. Apply the upgrade via the web UI: Administration > Software Updates > Software Installation, or via CLI: upgrade software
  7. 7. After upgrade completes, verify the version matches the fixed release and confirm the vulnerability is resolved
  8. 8. Validate that critical business functions work post-upgrade
Caveat Standard upgrade carries standard risk - ensure valid backup before proceeding; verify compatibility with any integrated systems

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

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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