dbcve.org
Secure Access Control SystemApplication · Cisco

CVE-2014-0650

HIGH · 10.0 CVSS v2.0 Published 2014-01-16
Fix available
A fix is available. Upgrade to after 5.4.0.46.2 or later.
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
The web interface in Cisco Secure Access Control System (ACS) 5.x before 5.4 Patch 3 allows remote attackers to execute arbitrary operating-system commands via a request to this interface, aka Bug ID CSCue65962.

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

Command injection vulnerability in Cisco Secure Access Control System (ACS) 5.x web interface allows remote attackers to execute arbitrary operating-system commands. The flaw exists in the web request handling, where unsanitized input is passed to OS-level command execution, enabling complete system compromise without authentication.

MitigationUpgrade Cisco ACS to version 5.4 Patch 3 or later. If immediate patching is not possible, restrict network access to the ACS web interface using network segmentation or firewall rules to limit exposure to untrusted networks.

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
Secure Access Control SystemApplication
Affected:<= 5.4.0.46.2= 5.1= 5.1.0.44= 5.1.0.44.1= 5.1.0.44.2= 5.1.0.44.3= 5.1.0.44.4= 5.1.0.44.5= 5.2= 5.2.0.26= 5.2.0.26.1= 5.2.0.26.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 ACS is installed
    Look for Cisco ACS processes or services running on the system. On the ACS appliance, log in and check running processes or review installed applications.
    Affected if Cisco ACS software is present on the system
  2. Determine the installed Cisco ACS version
    Access the ACS web interface and navigate to System Administration > Operations > Logs, or use the ACS CLI command 'show version' to retrieve the exact version number.
    Affected if The installed version matches any of the affected versions: 5.1, 5.1.0.44 through 5.1.0.44.5, 5.2, 5.2.0.26 through 5.2.0.26.2, or any version <= 5.4.0.46.2
  3. Confirm the ACS web interface is accessible
    Verify that the ACS web interface (HTTPS on port 443 or 8443 by default) is reachable from network vantage points. Check firewall rules or access lists that permit HTTP/HTTPS traffic to the ACS management IP.
    Affected if The web interface is exposed and reachable from any network where untrusted users could send requests
  4. Check for recent authentication activity
    Review ACS authentication and administration logs for any unexpected commands or unusual administrative actions, especially from the web interface endpoint.
    Affected if Unfamiliar commands or actions appear in logs that were not initiated by legitimate administrators

You are affected if Cisco ACS is installed, the version falls within 5.1 through 5.4.0.46.2, and the web interface is network-accessible.

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
Upgrade available Upgrade to a release after 5.4.0.46.2
Interim mitigation

Upgrade Cisco ACS to version 5.4 Patch 3 or later. If immediate patching is not possible, restrict network access to the ACS web interface using network segmentation or firewall rules to limit exposure to untrusted networks.

Recommended fix High confidence

Cisco Secure Access Control System 5.4 Patch 3 or later

  1. Review Cisco ACS 5.4 Patch 3 release notes and upgrade guide for compatibility and prerequisites
  2. Take a full backup of the current ACS configuration
  3. Ensure sufficient disk space and system resources for the upgrade
  4. Download Cisco ACS 5.4 Patch 3 or later from Cisco.com
  5. Schedule a maintenance window to minimize business impact
  6. Upload the patch file via the ACS web interface or CLI
  7. Apply the upgrade following Cisco's documented upgrade procedure
  8. Verify the upgrade was successful by checking the ACS version
Caveat Major version upgrades may require configuration migration testing; ensure backup and rollback plan are in place before proceeding

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

Fix this in Secure Access Control System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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