Summary
Vikunja deployments before 2.6.0 expose CalDAV BasicAuth endpoints without effective rate limiting, allowing unauthenticated attackers to make unbounded credential-guessing attempts. Successful guessing could compromise password-only accounts and provide access to associated data or actions.
Affected context
The vulnerability occurs in Vikunja's CalDAV-related BasicAuth routes when they are reachable remotely without a rate-limiting control that covers those endpoints. Affected request paths may include /dav, /.well-known, and /feeds; risk is higher for password-only accounts with weak or reused credentials.
Exploit preconditions
- Attack surface: Remotely reachable CalDAV and related BasicAuth endpoints
- Required access: No prior authentication is required
- Trigger point: Repeated authentication requests against the affected routes
- Why exploitation is possible: The endpoints may accept unbounded credential attempts without inheriting the instance's anti-brute-force protections
Why this happens
The underlying issue is inconsistent enforcement of authentication-attempt limits across protocol-specific endpoints. Although Vikunja may provide anti-brute-force controls elsewhere, the CalDAV BasicAuth paths do not adequately apply equivalent throttling or lockout behavior. This maps to CWE-307: Improper Restriction of Excessive Authentication Attempts, where an authentication mechanism permits repeated guesses without sufficient limiting controls.
Potential impact
- Attackers may compromise accounts protected only by passwords
- Unauthorized users could access private tasks, calendars, feeds, or other account data
- Compromised accounts could be used to alter, delete, or create application content
- Organizations may experience privacy violations, data manipulation, or account takeover
General mitigation guidance
Mitigation typically focuses on applying consistent, centralized authentication-abuse controls to every authentication-capable route, including protocol-specific endpoints.
Common defensive patterns include:
- Enforcing rate limits, progressive delays, and account or client throttling on CalDAV BasicAuth requests
- Ensuring anti-brute-force policies cover
/dav, discovery, and feed-related authentication paths - Using strong, unique credentials and reducing reliance on password-only authentication where stronger factors are available
- Applying secure session and credential policies with least privilege for user accounts
- Monitoring and restricting exposure of administrative or synchronization endpoints at network boundaries
How teams detect issues like this
Organizations can assess this issue through:
- Static and architectural reviews that compare authentication controls across web, API, CalDAV, and feed routes
- Code review searches for BasicAuth handlers that lack shared throttling or failure-accounting logic
- Dynamic testing that verifies repeated failed attempts are delayed, limited, logged, or temporarily blocked
- Policy checks requiring rate limiting for every externally reachable authentication endpoint
- Monitoring for bursts of failed authentication requests, distributed guessing patterns, and unusual access to synchronization paths
Automated security testing and code review tools may help identify authentication handlers that bypass centralized protections.

