CVE-2024-29296: A user enumeration vulnerability was found in Portainer CE 2.19.4.
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.
Security readout for executives and security teams
Plain-English summary
Portainer CE 2.19.4 may reveal whether usernames exist through timing differences during login. Attackers do not need credentials. The issue does not grant access by itself, but it can improve password-spraying, phishing, or targeted account attacks against exposed Portainer portals.
Executive priority
Treat this as a medium-priority hardening issue. It is unlikely to cause compromise alone, but exposed Portainer management portals are sensitive and username discovery can increase account-attack risk.
Technical view
The CVE describes a remote unauthenticated timing side channel in authentication that leaks account validity. CVSS 3.1 is 5.3: network-accessible, low complexity, no privileges, no user interaction, confidentiality impact only. Sources name Portainer CE 2.19.4 but do not list CPEs, broader affected versions, or a fixed release.
Likely exposure
Exposure is most relevant where Portainer CE 2.19.4 login pages are reachable by untrusted networks, especially the public internet. The provided sources do not confirm other affected versions.
Exploitation context
CISA KEV is false in the bundle, and no cited source states active exploitation. The described weakness could support account discovery before credential attacks, but it is not an authentication bypass.
Researcher notes
Evidence is limited to the CVE description and a GitHub reference. The bundle does not include vendor advisory details, fixed-version data, CPEs, or proof of exploitation. Avoid broad version claims without additional vendor confirmation.
Mitigation direction
Inventory Portainer deployments and identify any Portainer CE 2.19.4 instances.
Check Portainer guidance for confirmed affected versions and fixed releases.
Restrict Portainer login access to trusted networks or VPN paths.
Apply rate limiting and monitoring around authentication attempts.
Review account exposure and remove unused Portainer users.
Validation and detection
Confirm deployed Portainer edition and version from asset inventory.
Verify whether the Portainer login interface is internet reachable.
Review authentication logs for repeated invalid username probes.
Check vendor advisories for patch or configuration guidance.
Document compensating controls if no vendor fix is confirmed.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-286: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-286 · source CWE mapping
Incorrect User Management
Incorrect User Management represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.