---
id: "CVE-2024-5617"
kind: "vulnerability"
aliases: ["CVE-2024-5617"]
title: "Account lockout skipped on primary user store when usernames collide"
severity: "medium"
cvss: 4.8
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["account-lockout", "identity", "infrastructure", "user-store"]
not_affected_if: ["single-user-store", "unique-usernames"]
published_at: "2026-11-02T06:17:41+00:00"
first_seen_at: "2026-11-02T06:21:54+00:00"
updated_at: "2026-11-02T06:23:59+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-5617", "first_seen_at": "2026-11-02T06:21:54+00:00"}]
---

# Account lockout skipped on primary user store when usernames collide

When the same username exists in both a primary and a secondary user store, the account lock only applies to the secondary account. An attacker can keep guessing passwords against the primary account without being locked out.

_Summary, check and fix written by a model from the sources; labelled as such._

## Timeline

- 2026-11-02T06:21:54+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2024-5617

## From the sources

The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account.

This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_