Technical impact
Apache Iggy’s HTTP transport uses JSON Web Tokens that identify users only by a numeric user ID. When an administrator deletes a user, the numeric ID becomes available. If that user’s token remains unexpired or is refreshed before the ID is reassigned, the token authenticates as the next account created with the same ID, granting the attacker that account’s permissions. The flaw effectively allows an attacker to hijack authentication tokens and gain unauthorized access to another user’s account.
Affected Systems
Apache Iggy servers running version 0.9.0 or earlier and deploying the HTTP transport are affected. Only deployments with HTTP enabled are vulnerable. Versions through 0.9.0 are impacted; upgrading to 0.10.0 removes the issue.
Risk and Exploitability
The vulnerability enables an attacker to acquire the privileges of any user whose ID is reused, effectively performing account takeover. No EPSS score is available, but the lack of a KEV listing does not diminish the potential impact; the CVSS score is not supplied, yet the severity is inherently high due to the authentication bypass. The attack vector is the publicly accessible HTTP interface, implying that an adversary with network access to the service can exploit the flaw by presenting a valid, stale token or by refreshing it before the ID is reallocated. Overall, exploitation is straightforward in environments where user deletion and creation occur frequently.