CVE-2017-1286
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 · uneditedSensitive information about the configuration of the IBM UrbanCode Deploy 6.1 through 6.9.6.0 server and database can be obtained by a user who has been given elevated permissions in the UI, even after those elevated permissions have been revoked. IBM X-Force ID: 125147.
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 confidenceIBM UrbanCode Deploy versions 6.1 through 6.9.6.0 contain a permission revocation failure where users who were previously granted elevated permissions can continue to access sensitive server and database configuration information even after those permissions have been revoked through the UI. This appears to be a session or caching issue where authorization state is not properly updated upon permission changes.
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> 6.1, <= 6.9.6.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Verify IBM UrbanCode Deploy versionCheck the installed version through the admin console (About page) or the version.info file in the installation directory. Compare against the affected range: greater than 6.1 and up to 6.9.6.0.Affected if The installed version falls within 6.1 < version <= 6.9.6.0
-
Identify users with revoked elevated permissionsReview the user management section in the admin console to identify accounts that previously had elevated permissions (such as admin, system administrator, or configuration access roles) and those permissions were subsequently revoked.Affected if Any users exist in the system who had elevated permissions that were later revoked
-
Review access logs for post-revocation accessExamine server access logs (typically found in the logs directory) for requests to sensitive configuration endpoints (such as server configuration, database settings, or resource templates) from user accounts whose permissions were revoked. Look for access occurring after the timestamp of permission revocation.Affected if Logs show that users with revoked permissions continue to access sensitive configuration areas after their revocation
-
Inspect session persistenceCheck the server configuration for session timeout settings and examine whether active user sessions remain valid even after permission changes. Look for session cache or token storage mechanisms.Affected if Sessions established before permission revocation remain active and authorized
-
Audit configuration data accessReview audit logs or configuration change logs to determine if sensitive server or database configuration information was accessed by users who should no longer have those permissions.Affected if Users with revoked permissions successfully accessed sensitive configuration data
You are affected if your IBM UrbanCode Deploy version is between 6.1 and 6.9.6.0 and there are or were users with elevated permissions that were later revoked, particularly if those users may have active sessions.
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 relevant IBM patch for this vulnerability. Review access logs to identify any unauthorized access to configuration data that may have occurred during the window where elevated permissions should have been revoked, and rotate any exposed sensitive credentials.
- 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-2017-1286 — 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-2017-1286 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