CVE-2026-58271 @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
MediumCVSS 6.8
EPSS 0.22%
- Published
- Updated
- Exploit status
- No public exploit known
Description
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, POST /api/app/sync/register accepts credentials and a TOTP code to register a desktop sync client. On a failed TOTP, SyncClientsManager.register() calls updateAccesses(user, ip, false), which hits a freeze branch that writes passwordAttempts back unchanged. The counter never reaches USER_MAX_PASSWORD_ATTEMPTS (10) and the lockout gate never fires. A successful guess returns a {clientId, clientToken} pair. The token can be exchanged via POST /api/app/sync/auth/cookie for a full JWT. While the code is valid, the attacker can also call POST /api/auth/2fa/disable to permanently remove MFA. Version 2.4.0 patches the issue.
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| Sync-in server | = < 2.4.0 | No fix listed |
| Sync-in server(npm) | <= 2.3.0 | No fix listed |
References
- https://github.com/Sync-in/server/security/advisories/GHSA-274f-6w77-8qm9 exploit vendor-advisory
- nvd.nist.gov third-party-advisory
- github.com patch
- github.com patch
- github.com
- github.com