First published: Wed Sep 27 2017(Updated: )
** DISPUTED ** 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.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Freeipa Freeipa | =4.0.0 | |
Freeipa Freeipa | =4.0.1 | |
Freeipa Freeipa | =4.0.2 | |
Freeipa Freeipa | =4.0.3 | |
Freeipa Freeipa | =4.0.4 | |
Freeipa Freeipa | =4.0.5 | |
Freeipa Freeipa | =4.1.0 | |
Freeipa Freeipa | =4.1.1 | |
Freeipa Freeipa | =4.1.2 | |
Freeipa Freeipa | =4.1.3 | |
Freeipa Freeipa | =4.1.4 | |
Freeipa Freeipa | =4.2.0 | |
Freeipa Freeipa | =4.2.1 | |
Freeipa Freeipa | =4.2.2 | |
Freeipa Freeipa | =4.2.3 | |
Freeipa Freeipa | =4.2.4 | |
Freeipa Freeipa | =4.3.0 | |
Freeipa Freeipa | =4.3.1 | |
Freeipa Freeipa | =4.3.2 | |
Freeipa Freeipa | =4.3.3 | |
Freeipa Freeipa | =4.4.0 | |
Freeipa Freeipa | =4.4.1 | |
Freeipa Freeipa | =4.4.2 | |
Freeipa Freeipa | =4.4.3 | |
Freeipa Freeipa | =4.4.4 | |
Freeipa Freeipa | =4.5.0 | |
Freeipa Freeipa | =4.5.1 | |
Freeipa Freeipa | =4.5.2 | |
Freeipa Freeipa | =4.5.3 | |
Freeipa Freeipa | =4.6.0 | |
Freeipa Freeipa | =4.6.1 | |
=4.0.0 | ||
=4.0.1 | ||
=4.0.2 | ||
=4.0.3 | ||
=4.0.4 | ||
=4.0.5 | ||
=4.1.0 | ||
=4.1.1 | ||
=4.1.2 | ||
=4.1.3 | ||
=4.1.4 | ||
=4.2.0 | ||
=4.2.1 | ||
=4.2.2 | ||
=4.2.3 | ||
=4.2.4 | ||
=4.3.0 | ||
=4.3.1 | ||
=4.3.2 | ||
=4.3.3 | ||
=4.4.0 | ||
=4.4.1 | ||
=4.4.2 | ||
=4.4.3 | ||
=4.4.4 | ||
=4.5.0 | ||
=4.5.1 | ||
=4.5.2 | ||
=4.5.3 | ||
=4.6.0 | ||
=4.6.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.