Approved changes feed: RSS · Atom
cpe:2.3:a:sync-in:server:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Sync In (6a1e1bb4-dee9-5c5b-9571-e7766c0d91a4) |
|---|---|
| Product | Server (ba781720-7a28-55ce-b3ab-be0edefa016e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/sync-in/server |
purl2cpe | 2026-07-28 16:40:53.628315 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-58270 |
vulnerable | 2026-10-13 12:28:31.841282 |
Sync-in Server has a ReDoS via Unsanitized Regex in Sync Diff `pathFilters`
MEDIUM (6.5)
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, the sync diff endpoint compiles a user-supplied string into a `RegExp` with no complexity validation. A catastrophic-backtracking pattern (e.g. `^(a+)+b`) blocks the Node.js event loop, making the entire server unresponsive to all users until the container is restarted. Version 2.4.0 patches the issue.
Published: 2026-09-21T20:28:53.535Z
Updated: 2026-09-22T14:06:46.587Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-58271 |
vulnerable | 2026-10-13 12:28:31.557024 |
@sync-in/server vulnerable to TOTP Brute-Force via `POST /api/app/sync/register`
MEDIUM (6.8)
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.
Published: 2026-09-21T19:50:14.539Z
Updated: 2026-09-24T22:36:41.527Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-58269 |
vulnerable | 2026-10-13 12:28:31.533334 |
Sync-in Server has a complete 2FA Bypass via `POST /api/auth/token`
HIGH (8.1)
Sync-in Server is an open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.4.0, `POST /api/auth/token` authenticates with username and password only, then calls `getTokens()`, which returns full access and refresh JWTs without checking whether the account has TOTP 2FA enabled. An attacker with stolen or phished credentials can bypass 2FA in a single request. The parallel login endpoint (`POST /api/auth/login`) correctly enforces 2FA by calling `setCookies(user, res, true)`, which gates on `user.twoFaEnabled`. Version 2.4.0 patches the issue.
Published: 2026-09-21T20:01:56.322Z
Updated: 2026-09-24T22:38:27.013Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-47684 |
vulnerable | 2026-07-29 00:55:00.342212 |
Sync-in Server: SSRF protection bypass via IPv4-mapped IPv6 addresses in regExpPrivateIP
HIGH (7.7)
Sync-in Server is a secure, open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.3.0, the private IP blocklist regex used in the URL download feature does not match IPv4-mapped IPv6 addresses (e.g. ::ffff:127.0.0.1), allowing SSRF protection to be bypassed on dual-stack systems. Version 2.3.0 fixes the issue.
Published: 2026-06-16T14:31:30.807Z
Updated: 2026-06-16T17:10:12.548Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-41161 |
vulnerable | 2026-06-08 08:03:14.978167 |
Username Enumeration via Timing Attack
Sync-in Server is a secure, open-source platform for file storage, sharing, collaboration, and syncing. Prior to version 2.2.0, the /api/auth/login endpoint contains a logic flaw that allows unauthenticated remote attackers to enumerate valid usernames by measuring the application's response time. This issue has been patched in version 2.2.0.
Published: 2026-05-08T13:00:54.485Z
Updated: 2026-05-11T18:24:40.217Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.