{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-11191 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-11191 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-11191 is a high-severity vulnerability in n/a, published on 27 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-11191 and fix it if it is affected.\n\nWhat it is: CVE-2017-11191 is a high-severity vulnerability in n/a, published on 27 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-11191 in the wild and no public exploit code.\n\nAffected product: n/a. 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-11191/ (Markdown: https://insights.sbomify.com/CVE-2017-11191/index.md)","id":"CVE-2017-11191","markdown":"https://insights.sbomify.com/CVE-2017-11191/index.md","name":"CVE-2017-11191","record":{"aliases":["GHSA-h7qv-cfwh-6fxm"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"FreeIPA identity management","requires_auth":"low_privilege","summary":"Authenticated users may bypass account-locking restrictions by reusing old session IDs, though the vendor disputes this as a valid security issue.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"freeipa","vendor":"freeipa"}],"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":[{"id":"CWE-384","name":"Session Fixation"}],"description":"FreeIPA 4.x with API version 2.213 allows a remote authenticated users to bypass intended account-locking restrictions via an unlock action with an old session ID (for the same user account) that had been created for an earlier session. NOTE: Vendor states that issue does not exist in product and does not recognize this report as a valid security concern","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2017-11191","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2017-11193"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2017-11190"},"products":["n/a"],"published":"2017-09-27","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2015-5284","kev_date_added":null,"published":"2017-09-21"},{"cvss_score":9.6,"headline":"Freeipa: idm: ipa: freeipa: obtaining tgs with impersonating cname through trust relationships","id":"CVE-2026-11861","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":8.8,"headline":"Freeipa: delegation rules allow a proxy service to impersonate any user to access another target service","id":"CVE-2024-2698","kev_date_added":null,"published":"2024-06-12"},{"cvss_score":8.8,"headline":"Information disclosure in ipa","id":"CVE-2012-5631","kev_date_added":null,"published":"2019-11-25"},{"cvss_score":8.7,"headline":"Privilege escalation in Red Hat Enterprise Linux 10","id":"CVE-2026-13097","kev_date_added":null,"published":"2026-08-20"},{"cvss_score":8.2,"headline":"Missing authorization in Red Hat Enterprise Linux 10","id":"CVE-2026-19550","kev_date_added":null,"published":"2026-08-11"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Authenticated users may bypass account-locking restrictions by reusing old session IDs, though the vendor disputes this as a valid security issue.","url":"https://insights.sbomify.com/CVE-2017-11191/"}