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.

Project Subscriptions

Vendors Products
Sync-in Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-274f-6w77-8qm9 @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Fri, 25 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 21 Sep 2026 21:45:00 +0000

Type Values Removed Values Added
First Time appeared Sync-in
Sync-in server
Vendors & Products Sync-in
Sync-in server

Mon, 21 Sep 2026 20:00:00 +0000

Type Values Removed Values Added
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.
Title @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
Weaknesses CWE-307
References
Metrics cvssV3_1

{'score': 6.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-24T22:36:41.527Z

Reserved: 2026-06-29T21:54:30.332Z

Link: CVE-2026-58271

cve-icon Vulnrichment

Updated: 2026-09-24T22:36:36.851Z

cve-icon NVD

Status : Deferred

Published: 2026-09-21T20:17:26.993

Modified: 2026-09-24T23:17:12.723

Link: CVE-2026-58271

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-21T22:15:17Z

Weaknesses