Identity Services Engine SoftwareApplication · Cisco

CVE-2013-5521

MEDIUM · 5.0 CVSS v2.0 Published 2013-10-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
Cisco Identity Services Engine does not properly restrict the creation of guest accounts, which allows remote attackers to cause a denial of service (exhaustion of the account supply) via a series of requests within one session, aka Bug ID CSCue94287.

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 confidence

Cisco Identity Services Engine (ISE) fails to properly restrict guest account creation within a single session, allowing remote attackers to repeatedly create guest accounts until the account supply is exhausted, causing denial of service.

MitigationImplement rate limiting or session-based constraints on guest account creation in Cisco ISE; apply vendor patches when available.

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
Identity Services Engine SoftwareApplication
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
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Cisco ISE is deployed
    Check for Cisco ISE processes, services, or installation directories on the system. On network devices, verify if ISE is configured as an authentication/authorization server.
    Affected if Cisco Identity Services Engine is present and running in the environment
  2. Verify guest user provisioning is enabled
    Access the Cisco ISE administration console and navigate to Guest > Guest Settings, or inspect the ISE configuration via CLI/API for guest user management settings.
    Affected if Guest user account creation is enabled in Cisco ISE
  3. Check for rate limiting on guest account creation
    Inspect Cisco ISE configuration for rate limit settings under Guest > Settings > Guest Type configuration, or check for policy elements related to account creation throttling.
    Affected if No rate limiting or throttling is configured for guest account creation requests
  4. Check for session-based constraints on guest flows
    Review ISE policy configurations for session limits, concurrent session restrictions, or account creation quotas applied to guest user flows.
    Affected if No session-based constraints or account quotas are enforced on guest user creation
  5. Review guest account quota limits
    Check the maximum number of guest accounts allowed in the ISE system under Administration > System > Settings > Guest Settings, or verify if account supply limits are defined.
    Affected if No maximum guest account limits are configured or the system allows unlimited guest account creation

The environment is affected if Cisco ISE is running with guest user creation enabled and without rate limiting, session constraints, or account quota restrictions configured.

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

Implement rate limiting or session-based constraints on guest account creation in Cisco ISE; apply vendor patches when available.

Fix this in Identity Services Engine Software 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 help mitigating

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-2013-5521 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-5521 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