# CVE-2024-29296: Portainer CE allows username enumeration through authentication response timing

> Remote attackers can enumerate valid usernames in Portainer CE by analyzing authentication response time differences.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Apr 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-87x6-8m9v-g8c2, GO-2026-6619

## What is CVE-2024-29296?

CVE-2024-29296 is a medium-severity vulnerability in n/a, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A user enumeration vulnerability was found in Portainer CE 2.19.4. This issue occurs during user authentication process, where a difference in response time could allow a remote unauthenticated user to determine if a username is valid or not.

Weakness: CWE-286 (Incorrect User Management)

## Which versions are affected by CVE-2024-29296?

3 open source packages ship an affected version, including github.com/portainer/portainer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/portainer/portainer` | Go | All versions | 0.6.1-0.20240417040827-48bc7d0d92f0 |
| `github.com/portainer/portainer` | Go | All versions | 0.6.1-0.20240417040827-48bc7d0d92f0 |
| `github.com/portainer/portainer` | Go | All versions | 0.6.1-0.20240417040827-48bc7d0d92f0 |

Products: Portainer Portainer.

## How do I fix CVE-2024-29296?

Upgrade github.com/portainer/portainer to 0.6.1-0.20240417040827-48bc7d0d92f0 or later.

## Is CVE-2024-29296 being exploited?

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

Public exploit code:

- CVE-2024-29296 - User enumeration on Portainer CE - 2.19.4 (github_poc): https://github.com/ThaySolis/CVE-2024-29296
- User Enumeration through response time difference (github_poc): https://github.com/Lavender-exe/CVE-2024-29296-PoC

## Other vulnerabilities in n/a

- [CVE-2019-16872](https://insights.sbomify.com/CVE-2019-16872/): Missing authorization in n/a (critical 9.9)
- [CVE-2022-24961](https://insights.sbomify.com/CVE-2022-24961/): Missing authorization in n/a (critical 9.8)
- [CVE-2020-24264](https://insights.sbomify.com/CVE-2020-24264/): Missing authorization in n/a (critical 9.8)
- [CVE-2018-19466](https://insights.sbomify.com/CVE-2018-19466/): Information disclosure in n/a (critical 9.8)
- [CVE-2018-19367](https://insights.sbomify.com/CVE-2018-19367/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-29296 and fix it if it is affected.

What it is: CVE-2024-29296 is a medium-severity vulnerability in n/a, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-29296 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/portainer/portainer (Go): affected all versions; fixed in 0.6.1-0.20240417040827-48bc7d0d92f0
- github.com/portainer/portainer (Go): affected all versions; fixed in 0.6.1-0.20240417040827-48bc7d0d92f0
- github.com/portainer/portainer (Go): affected all versions; fixed in 0.6.1-0.20240417040827-48bc7d0d92f0

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-2024-29296/ (Markdown: https://insights.sbomify.com/CVE-2024-29296/index.md)
```

## Sources

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

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