Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-58270 medium CVSS 6.5

Vulnerability in @sync-in/server (CVE-2026-58270)

Summary

Vulnerability in @sync-in/server (CVE-2026-58270). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/app/sync/operation/diff/. Mitigation: upgrade to 2.4.0 or later.

Original description

The description as published by the source.

Affected component: Sync-in Server v2.3.0, POST /api/app/sync/operation/diff/:id, vulnerable implementation of pathFilters in backend/src/applications/sync/dtos/sync-operations.dto.ts.

Summary

In the vulnerable version, the sync diff endpoint accepted a user-controlled regex pattern through pathFilters and compiled it into a RegExp without complexity validation. The resulting regex was then executed synchronously against relative file paths during diff generation.

A catastrophic-backtracking pattern, such as ^(a+)+b, can block the affected Node.js event loop when evaluated against a worst-case path shape. In a single-process deployment, this can make the server unavailable to other users while the regex evaluation is running. Repeated malicious requests can sustain the denial of service.

Details

SyncDiffDto transformed user input directly into a RegExp without validating regex complexity:

// backend/src/applications/sync/dtos/sync-operations.dto.ts
@IsOptional()
@Transform(({ value }) => (typeof value === 'string' && value.length > 0 ? new RegExp(value, 'i') : null))
pathFilters?: RegExp = null

The compiled regex was then executed synchronously during sync diff traversal:

// backend/src/applications/sync/services/sync-manager.service.ts
if (ctx.syncDiff.pathFilters && ctx.syncDiff.pathFilters.test(filePath)) {

Because .test() is synchronous, a catastrophic-backtracking pattern can block the Node.js event loo…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-58270 has been found in @sync-in/server.
Attackers can target a specific entry point like POST /api/app/sync/operation/diff/ over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.5/10.
What to do: upgrade @sync-in/server to 2.4.0 or later.
If unsure, ask your IT team or search "@sync-in/server CVE-2026-58270" on the vendor's site.

CVE-2026-58270 (@sync-in/server) — CWE-1333 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/app/sync/operation/diff/ / POST /api/app/sync/register / POST /api/app/sync/auth/cookie / POST /api/app/sync/operation/diff/1
Patched: 2.4.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-1333) exists in @sync-in/server. Attackers reach the vulnerable code path via POST /api/app/sync/operation/diff/.

📍 Affected scope

Check the vendor advisory for the affected versions of @sync-in/server. Attack surface: POST /api/app/sync/operation/diff/ / POST /api/app/sync/register / POST /api/app/sync/auth/cookie / POST /api/app/sync/operation/diff/1.

🔥 Severity

Severity: Medium (CVSS 6.5/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.4.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /api/app/sync/operation/diff/ requests with malformed payloads or SQL meta-characters. Run grep -r '@sync-in/server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@sync-in/server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @sync-in/server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /api/app/sync/operation/diff/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /api/app/sync/operation/diff/ への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch 
    Upgrade @sync-in/server to 2.4.0

    ステージング環境で 2.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /api/app/sync/operation/diff/ on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm @sync-in/server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details