Identity Services EngineApplication · Cisco
CVE-2024-20332
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 · uneditedA vulnerability in the web-based management interface of Cisco Identity Services Engine (ISE) could allow an authenticated, remote attacker to conduct a server-side request forgery (SSRF) attack through an affected device. This vulnerability is due to improper input validation for specific HTTP requests. An attacker could exploit this vulnerability by sending a crafted HTTP request to an affected device. A successful exploit could allow the attacker to send arbitrary network requests that are sourced from the affected device. To successfully exploit this vulnerability, the attacker would need valid Super Admin credentials.
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 confidenceSSRF vulnerability in Cisco ISE's web-based management interface due to improper input validation in specific HTTP requests. An authenticated attacker with Super Admin credentials can send crafted HTTP requests to cause the device to make arbitrary network requests on the attacker's behalf, potentially reaching internal systems.
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 EngineApplication
= 3.2.0= 3.3.0CVSS 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
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
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 ISE is installedIdentify if Cisco Identity Services Engine is running on the system by checking for ISE-related processes or services (such as 'ise' or 'cisco-ise' processes) using system process listing tools.Affected if Cisco ISE software is not present on the system.
-
Determine the installed ISE versionAccess the ISE web administration interface and navigate to the Administration > System > Settings > Software Updates > Updates page, or use the CLI command 'show version' to retrieve the running software version.Affected if The installed version matches 3.2.0 or 3.3.0 specifically.
-
Verify web-based management interface is enabledCheck if the ISE web administration interface (HTTPS on port 443 or 8443) is accessible and operational by attempting to reach the login page.Affected if The web management interface is disabled and not accessible.
-
Identify Super Admin accountsLog into the ISE web interface and navigate to Administration > Identity Management > Identities > Users to view Super Admin accounts, or use the CLI command 'show running-config | include user' to list configured administrative accounts.Affected if No Super Admin accounts are configured.
-
Review ISE logs for suspicious HTTP requestsExamine ISE logs located in the /opt/ise/logs directory or via the web interface under Operations > RADIUS > Live Logs, looking for unusual HTTP requests, especially those to internal IP addresses or unusual destinations originating from the ISE management interface.Affected if No suspicious outbound HTTP requests are observed in the logs.
The environment is affected only if Cisco ISE versions 3.2.0 or 3.3.0 are installed, the web management interface is enabled, and Super Admin accounts exist that could be exploited to send crafted HTTP requests.
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 dataApply the vendor patch from Cisco for this vulnerability. Additionally, restrict Super Admin account access, implement network segmentation, and monitor ISE logs for suspicious HTTP request patterns.
Fix this in Identity Services Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.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 $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20332 — 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-2024-20332 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