Summary
Frigate NVR versions prior to 0.17.0-beta1 allow any authenticated user to change their own password via the /users/{username}/password endpoint without verifying the current password, and do not enforce password strength or invalidate existing JWT tokens after a password change.
If an attacker acquires a victim's valid JWT or session cookie, they can silently change the victim's password, maintain long-term account control, and continue to use stolen tokens even after subsequent password resets, while weak passwords remain susceptible to brute-force attempts.
Affected context
This vulnerability arises in Frigate NVR deployments where user authentication is handled via JWT tokens and the /users/{username}/password endpoint is exposed to authenticated clients.
It is relevant when:
- Users authenticate using tokens that can be reused over extended periods
- The application allows password changes without requiring the current password
- Password changes do not invalidate existing JWTs or active sessions
- Password strength requirements are weak or absent
Any environment where tokens may be exposed (e.g., shared devices, unencrypted HTTP, browser XSS, or misconfigured logging) is especially at risk.
Exploit preconditions
- Attack surface: Authenticated HTTP API endpoint
/users/{username}/password - Required access: A valid JWT or session cookie for the target account (e.g., obtained via leakage, XSS, compromised device, sniffing over HTTP, or other theft)
- Trigger point: Issuing a password change request for the victim's account without needing the current password
- Why exploitation is possible:
- The password change workflow does not verify knowledge of the existing password, so possession of a token alone is treated as sufficient for permanent credential changes.
- JWT tokens are not revoked or rotated after password changes, allowing hijacked sessions to persist indefinitely.
- No password strength enforcement means an attacker can set weak passwords or brute-force them more easily.
Why this happens
The core issue maps to CWE-287: Improper Authentication and related authentication workflow design flaws.
The password change endpoint equates "having a valid token" with "full proof of identity," omitting an additional authentication factor such as the current password or recent credential confirmation.
This breaks a common security invariant: credential changes should require re-verification of identity.
Additionally, the authentication subsystem does not bind JWT validity to credential state, so tokens remain valid even when underlying passwords change.
The absence of password complexity or strength checks further weakens authentication by allowing easily guessable credentials, increasing exposure to brute-force and credential stuffing patterns.
Potential impact
- An attacker with a stolen JWT or cookie can change a victim's password and lock the legitimate user out of their account.
- Persistent session hijacking, where stolen tokens continue to work even after the user resets their password.
- Long-term, stealthy access to video feeds, recordings, and configuration data within Frigate NVR.
- Ability to modify security-sensitive settings (e.g., camera configuration, storage, or integrations).
- Elevated risk of successful password guessing attacks due to lack of password strength validation.
- Compromise of downstream systems integrated with Frigate if shared credentials or tokens are reused.
General mitigation guidance
Effective mitigation focuses on strengthening authentication workflows and coupling session tokens to credential state:
- Require verification of the current password (or an equivalent strong factor) before allowing password changes or other critical account modifications.
- Invalidate or rotate JWT tokens and active sessions whenever a password or primary authentication factor is changed, ideally forcing re-authentication across all devices.
- Introduce password strength policies (e.g., minimum length, complexity, common-password checks, and rate limiting) to reduce susceptibility to brute-force attacks.
- Implement session management practices that keep token lifetimes short, support logout-all-sessions behavior, and bind tokens to relevant context (e.g., device, IP, or risk-based checks).
- Apply least-privilege design for API endpoints, ensuring user-management endpoints perform strict subject checks and enforce robust authorization.
- Encourage secure deployment practices such as enforcing HTTPS, secure cookie flags, and isolation of NVR interfaces from untrusted networks.
How teams detect issues like this
Detection approaches can focus on both code-level and behavioral signals:
- Static analysis and code review:
- Flag password change or credential update endpoints that do not verify the current password or a strong authentication factor.
- Review session and token management logic to ensure token invalidation is tied to password changes and other high-risk events.
- Search for missing or minimal password policy checks, such as absent validation around length, complexity, or banned password lists.
- Configuration and policy enforcement:
- Enforce security requirements for authentication workflows via coding standards and API design guidelines (e.g., "all password changes require current password").
- Use automated review tools or linters to detect common authentication anti-patterns, such as long-lived tokens without revocation mechanisms.
- Runtime monitoring:
- Monitor logs for unusual patterns, such as multiple password changes from different IPs or devices, or high-frequency login attempts against the same account.
- Implement alerts for password changes occurring shortly after new logins from atypical locations or user agents.

