@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Sync-in | server | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Sync-in | Server |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-274f-6w77-8qm9 | @sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register` |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.219% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Sync-in
Sync-in server |
|
| Vendors & Products |
Sync-in
Sync-in server |
| 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
|