Secure Access Control SystemApplication · Cisco
CVE-2014-2130
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 · uneditedCisco Secure Access Control Server (ACS) provides an unintentional administration web interface based on Apache Tomcat, which allows remote authenticated users to modify application files and configuration files, and consequently execute arbitrary code, by leveraging administrative privileges, aka Bug ID CSCuj83189.
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 confidenceCisco Secure Access Control Server (ACS) exposes an unintentional administration web interface based on Apache Tomcat. Remote authenticated users with administrative privileges can modify application files and configuration files through this interface, leading to arbitrary code execution.
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
all versionsCVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify ACS web interface exposureReview network accessibility of Cisco ACS web interfaces. Check firewall rules, ACLs, and NAT configurations to determine if the ACS administrative web interface is reachable from external or untrusted networks.Affected if The ACS web interface is accessible from networks other than trusted administrative networks.
-
Check for exposed Tomcat management endpointsAttempt to access common Tomcat management paths on the ACS server: /manager/html, /manager/status, /host-manager/html, /admin. Use a web browser or curl to request these endpoints.Affected if Any Tomcat-specific management interface returns a valid response (not 404) instead of being blocked.
-
Verify administrative user accessLog into the Cisco ACS web interface with an administrative account. Navigate to Users and Identity Stores to confirm the account has full administrative privileges.Affected if The authenticated user account has Administrative or Super Admin role permissions.
-
Inspect Tomcat configuration filesOn the ACS server, examine the server.xml file in the Tomcat conf directory for context definitions. Look for <Context> entries that expose the /manager, /admin, or /host-manager paths.Affected if Tomcat context definitions allow access to management interfaces without proper restriction.
The environment is affected if the Cisco ACS web interface is accessible to authenticated administrators and any Tomcat management endpoints (/manager, /admin, /host-manager) are exposed alongside the intended ACS admin interface.
Generated from the published advisory. Verify against your own configuration.
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 dataDisable or remove the unintended Tomcat administration interface from Cisco ACS and apply the vendor patch for CSCuj83189. Restrict administrative web interface access to authorized networks/IPs.
Fix this in Secure Access Control System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2014-2130 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2130 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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