{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-1539 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-1539 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-1539 is a high-severity vulnerability in Ibm Business Process Manager, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-1539 and fix it if it is affected.\n\nWhat it is: CVE-2017-1539 is a high-severity vulnerability in Ibm Business Process Manager, published on 26 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-1539 in the wild and no public exploit code.\n\nAffected product: Ibm Business Process Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-1539/ (Markdown: https://insights.sbomify.com/CVE-2017-1539/index.md)","id":"CVE-2017-1539","markdown":"https://insights.sbomify.com/CVE-2017-1539/index.md","name":"CVE-2017-1539","record":{"aliases":["GHSA-3xh8-3p84-p59c"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Business Process Manager","requires_auth":"low_privilege","summary":"Attackers can gain privileged access by manipulating LDAP group memberships due to improper distinction between internal and user registry groups.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"business_process_manager","vendor":"ibm"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Privilege escalation in Business Process Manager Advanced","id":"CVE-2017-1539","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:business_process_manager","products":["ibm:business_process_manager"],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Rational DOORS","id":"CVE-2017-1540"},"packages":[],"prev":{"headline":"Information disclosure in IBM Financial Transaction Manager","id":"CVE-2017-1538"},"products":["Business Process Manager Advanced"],"published":"2017-09-26","related":[{"cvss_score":9,"headline":"Code injection in n/a","id":"CVE-2015-1961","kev_date_added":null,"published":"2015-07-13"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Business Process Manager","id":"CVE-2017-1769","kev_date_added":null,"published":"2018-01-24"},{"cvss_score":8.1,"headline":"XML external entity in Business Process Manager Advanced","id":"CVE-2017-1527","kev_date_added":null,"published":"2017-09-26"},{"cvss_score":6.8,"headline":"Weak cryptography in n/a","id":"CVE-2015-7441","kev_date_added":null,"published":"2016-01-01"},{"cvss_score":6.5,"headline":"Missing authorization in Business Process Manager","id":"CVE-2017-1628","kev_date_added":null,"published":"2017-11-27"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2015-0110","kev_date_added":null,"published":"2017-09-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["IBM"]},"summary":"Attackers can gain privileged access by manipulating LDAP group memberships due to improper distinction between internal and user registry groups.","url":"https://insights.sbomify.com/CVE-2017-1539/"}