CVE-2017-1539
Last modified
CVE-2017-1539 is a vulnerability of currently unknown severity. IBM Business Process Manager 7.5, 8.0, and 8.5 is vulnerable to privilege escalation by not properly distinguishing internal group memberships from user registry group memberships. By manipulating LDAP group membership an attack might gain privileged access. EPSS estimates a 1.52% chance of exploitation in the next 30 days.
Description
IBM Business Process Manager 7.5, 8.0, and 8.5 is vulnerable to privilege escalation by not properly distinguishing internal group memberships from user registry group memberships. By manipulating LDAP group membership an attack might gain privileged access. IBM X-Force ID: 130807.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Ibm | Business Process Manager | 7.5.0.0 |
| Ibm | Business Process Manager | 7.5.0.1 |
| Ibm | Business Process Manager | 7.5.1.0 |
| Ibm | Business Process Manager | 7.5.1.1 |
| Ibm | Business Process Manager | 7.5.1.2 |
| Ibm | Business Process Manager | 8.0.0.0 |
| Ibm | Business Process Manager | 8.0.1.0 |
| Ibm | Business Process Manager | 8.0.1.1 |
| Ibm | Business Process Manager | 8.0.1.2 |
| Ibm | Business Process Manager | 8.0.1.3 |
| Ibm | Business Process Manager | 8.5.0.0 |
| Ibm | Business Process Manager | 8.5.0.1 |
| Ibm | Business Process Manager | 8.5.0.2 |
| Ibm | Business Process Manager | 8.5.5.0 |
| Ibm | Business Process Manager | 8.5.6.0 |
| Ibm | Business Process Manager | 8.5.6.1 |
| Ibm | Business Process Manager | 8.5.6.2 |
| Ibm | Business Process Manager | 8.5.7.0 |
References
- http://www.ibm.com/support/docview.wss?uid=swg22007451Patch, Vendor Advisory
- http://www.securityfocus.com/bid/100967Third Party Advisory, VDB Entry
- https://exchange.xforce.ibmcloud.com/vulnerabilities/130807VDB Entry, Vendor Advisory
- http://www.ibm.com/support/docview.wss?uid=swg22007451Patch, Vendor Advisory
- http://www.securityfocus.com/bid/100967Third Party Advisory, VDB Entry
- https://exchange.xforce.ibmcloud.com/vulnerabilities/130807VDB Entry, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1539?
How severe is CVE-2017-1539?
How do I fix CVE-2017-1539?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-15384rate-me.php in Rate Me 1.0 has XSS via the id field in a rat…
- CVE-2017-15385The store_versioninfo_gnu_verdef function in libr/bin/format…
- CVE-2017-15386Incorrect implementation in Blink in Google Chrome prior to …
- CVE-2017-15387Insufficient enforcement of Content Security Policy in Blink…
- CVE-2017-15388Iteration through non-finite points in Skia in Google Chrome…
- CVE-2017-15389An insufficient watchdog timer in navigation in Google Chrom…
- CVE-2017-15390Insufficient Policy Enforcement in Omnibox in Google Chrome …
- CVE-2017-15391Insufficient Policy Enforcement in Extensions in Google Chro…
- CVE-2017-15392Insufficient data validation in V8 in Google Chrome prior to…
- CVE-2017-15393Insufficient Policy Enforcement in Devtools remote debugging…
- CVE-2017-15394Insufficient Policy Enforcement in Extensions in Google Chro…
- CVE-2017-15395A use after free in Blink in Google Chrome prior to 62.0.320…
Are you affected by CVE-2017-1539?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
