Secure Access Control SystemApplication · Cisco
CVE-2013-1200
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 · uneditedSession fixation vulnerability in Cisco Secure Access Control System (ACS) allows remote attackers to hijack web sessions via unspecified vectors, aka Bug ID CSCud95787.
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 · moderate confidenceSession fixation vulnerability in Cisco Secure Access Control System allows remote attackers to potentially hijack web sessions by setting or predicting session identifiers before user authentication, then leveraging that fixed ID to intercept or impersonate legitimate user sessions.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/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.
-
Confirm Cisco Secure Access Control System is deployedReview your infrastructure inventory or check for the Cisco ACS web interface/service running on your networkAffected if The product is present in the environment, making it vulnerable since all versions are affected
-
Identify session management configurationLocate the ACS administrative interface or configuration files that govern web session behaviorAffected if Session configuration exists and cannot be verified to enforce ID regeneration on login
-
Check session ID generation mechanismReview ACS logs or configuration for how session identifiers are created - look for evidence of predictable or static session IDsAffected if Session IDs are generated before authentication or do not change after successful login
-
Verify session invalidation on logoutTest the logout function - clear your session, authenticate again, and check if a new session ID is issuedAffected if The same session ID persists across logout/login cycles or after authentication
-
Inspect session timeout and entropy settingsExamine ACS security settings for session timeout values and random number generation configurationAffected if Sessions have excessive timeouts or weak entropy is used for ID generation
You are affected if Cisco Secure Access Control System is deployed and session IDs are not regenerated upon successful authentication, allowing an attacker to pre-establish a session ID before login.
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 dataImplement session ID regeneration upon successful authentication, enforce session invalidation on logout, and review Cisco ACS session management configuration for proper entropy and timeout settings.
Fix this in Secure Access Control System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1200 — 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-2013-1200 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