CVE-2015-0757
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 · uneditedThe web framework in Cisco Identity Services Engine (ISE) 1.2(1.901) and 1.3(0.722) does not properly implement session handlers, which allows remote attackers to obtain sensitive information by reading web pages, as demonstrated by MnT reports, aka Bug ID CSCuq23140.
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 confidenceThe Cisco ISE web framework has improper session handler implementation, allowing remote attackers to read sensitive information through web pages, specifically via MnT (Monitoring and Troubleshooting) reports. This session management weakness could allow unauthorized access to session data or session hijacking.
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= 1.2\(1.901\)= 1.3\(0.722\)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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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.
-
Identify the installed Cisco ISE versionLog into the Cisco ISE CLI and run the command 'show version' or access the ISE admin web interface and navigate to Administration > System > Settings > Product Version to retrieve the exact software versionAffected if The version displayed matches exactly 1.2(1.901) or 1.3(0.722)
-
Confirm MnT node is configuredIn the ISE admin web interface, go to Administration > System > Deployment and check if any node is designated as the Monitoring and Troubleshooting (MnT) node, or use the CLI command 'show application status ise' to identify active MnT servicesAffected if An MnT node is deployed and the MnT web service is running
-
Verify MnT web interface accessibilityAttempt to access the MnT reporting interface by navigating to https://<ISE-hostname>/mnt via a web browser, or check the ISE configuration under Administration > System > Settings > Logging > Logging Settings to confirm MnT reporting is enabledAffected if The MnT web interface is accessible and responds to requests
-
Review session handling configurationIn the ISE admin web interface, navigate to Administration > System > Admin User Settings > Session Settings to inspect session timeout and session management configurationsAffected if Session settings are present but the version is vulnerable (1.2(1.901) or 1.3(0.722)) regardless of specific session settings
You are affected if your Cisco ISE installation is exactly version 1.2(1.901) or 1.3(0.722) and the MnT (Monitoring and Troubleshooting) web interface is accessible.
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 Cisco ISE patches for versions 1.2(1.901) and 1.3(0.722) or upgrade to a supported version. If patching is delayed, restrict network access to the ISE administrative web interface to trusted management networks.
- 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-2015-0757 — 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-2015-0757 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