# CVE-2017-11191: Security feature bypass in n/a

> Authenticated users may bypass account-locking restrictions by reusing old session IDs, though the vendor disputes this as a valid security issue.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-h7qv-cfwh-6fxm

## What is CVE-2017-11191?

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.

### Official 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

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2017-11191?

It affects 1 product.


Products: Freeipa Freeipa.

## How do I fix CVE-2017-11191?

No fix has been published for CVE-2017-11191 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-11191 being exploited?

There is no known exploitation of CVE-2017-11191 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2015-5284](https://insights.sbomify.com/CVE-2015-5284/): Information disclosure in n/a (critical 9.8)
- [CVE-2026-11861](https://insights.sbomify.com/CVE-2026-11861/): Freeipa: idm: ipa: freeipa: obtaining tgs with impersonating cname through trust relationships (critical 9.6)
- [CVE-2024-2698](https://insights.sbomify.com/CVE-2024-2698/): Freeipa: delegation rules allow a proxy service to impersonate any user to access another target service (high 8.8)
- [CVE-2012-5631](https://insights.sbomify.com/CVE-2012-5631/): Information disclosure in ipa (high 8.8)
- [CVE-2026-13097](https://insights.sbomify.com/CVE-2026-13097/): Privilege escalation in Red Hat Enterprise Linux 10 (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-11191 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2017-11191 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-11191/ (Markdown: https://insights.sbomify.com/CVE-2017-11191/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-11191
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-11191
- OSV: https://osv.dev/vulnerability/CVE-2017-11191

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-11191/
Summaries are generated and may contain mistakes; the official description above is the record.