Summary
Vikunja authentication endpoints do not consistently enforce rate limits, allowing remote unauthenticated attackers to submit unlimited requests. This can support credential guessing, account enumeration, and password-reset flooding against exposed login, registration, reset, and OAuth token routes.
Affected context
The vulnerability occurs in Vikunja deployments that expose the affected public authentication endpoints without effective request throttling. Risk is higher when these routes are reachable from untrusted networks and when no compensating controls, such as an appropriately configured reverse proxy, web application firewall, or identity protection service, limit repeated requests.
Exploit preconditions
- Attack surface: Public HTTP API authentication and account-management endpoints
- Required access: No authentication is required; network reachability to the exposed routes is sufficient
- Trigger point: Repeated requests to login, registration, password-reset, or OAuth token endpoints
- Why exploitation is possible: The endpoints accept repeated authentication-related requests without applying effective per-account, per-source, or global throttling controls
Why this happens
The underlying issue is insufficient restriction of repeated authentication attempts, mapping to CWE-307: Improper Restriction of Excessive Authentication Attempts. The affected endpoints lack a consistently enforced rate-limiting policy, allowing automated clients to send high-volume requests without meaningful delay, lockout, or adaptive challenge mechanisms. This insecure pattern increases the feasibility of credential guessing, account discovery, and abuse of password-reset workflows.
Potential impact
- Attackers may perform large-scale credential guessing
- User accounts could be compromised when weak or reused passwords are targeted
- Attackers could enumerate valid accounts through response or timing differences
- Password-reset workflows may be flooded, causing notification abuse or denial of service
- Authentication infrastructure could experience increased load
General mitigation guidance
Mitigation generally focuses on enforcing layered, risk-aware throttling across every public authentication workflow.
Common defensive patterns include:
- Applying per-source, per-account, per-device, and global request limits
- Using progressive delays, temporary challenges, or adaptive verification after repeated failures
- Returning consistent responses for valid and invalid account identifiers
- Limiting password-reset requests and making reset operations safe to repeat
- Placing an appropriately configured reverse proxy or web application firewall in front of public endpoints
- Monitoring authentication abuse and applying least privilege to supporting service accounts
- Reducing reliance on client-controlled identifiers when selecting rate-limit buckets
How teams detect issues like this
Organizations can identify this weakness through:
- Static and configuration analysis for authentication routes without throttling middleware
- Code review checks confirming that login, registration, reset, and token flows share consistent abuse controls
- Dynamic testing that measures behavior under repeated failed and successful requests
- Monitoring for bursts of authentication failures, account-discovery patterns, and repeated reset requests
- Policy enforcement requiring documented rate limits and alerting for every public authentication endpoint
- Neutral automated security review tools that flag missing or inconsistently applied rate-limiting controls

