CVE-2014-3275
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 · uneditedSQL injection vulnerability in the web framework in Cisco Identity Services Engine (ISE) 1.2(.1 patch 2) and earlier allows remote authenticated users to execute arbitrary SQL commands via a crafted URL, aka Bug ID CSCul21337.
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 confidenceSQL injection vulnerability in the web framework of Cisco Identity Services Engine (ISE) allows remote authenticated users to execute arbitrary SQL commands via crafted URL parameters. The vulnerability exists in version 1.2(.1 patch 2) and earlier, indicating unsanitized user input is passed directly into SQL queries.
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.0= 1.1CVSS 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 the installed Cisco ISE versionAccess the ISE administration GUI and navigate to Administration > System > Settings > Product Version, or use the CLI command 'show version' to display the running software versionAffected if The displayed version is 1.0, 1.1, or 1.2 (including 1.2.1 patch 2 or earlier)
-
Confirm the ISE web interface is enabledVerify that the ISE web portal service is running by checking the administration GUI status page or using the CLI command 'show application status ise'Affected if The web framework services are active and accessible
-
Review web server logs for SQL injection indicatorsExamine ISE logs located in the support directory for unusual SQL syntax patterns in URL parameters, looking for keywords such as 'UNION', 'SELECT', 'INSERT', or common SQL injection characters (' or 1=1, etc.) in request logsAffected if Logs contain SQL-like error messages or suspicious URL patterns resembling SQL injection attempts
-
Check the current patch levelIn the ISE administration GUI, navigate to Administration > System > Upgrade > Patch Installation Status to view installed patches, or use the CLI command 'show patch'Affected if No patches addressing CSCul21337 have been installed, or the patch history shows the system is below the fixed release
A user is affected if Cisco ISE version 1.0, 1.1, or 1.2 (including 1.2.1 patch 2 or earlier) is running, the web interface is exposed, and no vendor patch for CSCul21337 has been applied.
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 for Cisco ISE (Bug ID CSCul21337). Until patched, restrict access to the ISE web interface to only trusted, authorized personnel and monitor for suspicious SQL-like error patterns in logs.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2014-3275 — 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-3275 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