docs: scan #110 — can4hou6joeng4/boss-agent-cli (browser-bridge loopback, filed private)

[elfrost]

Scan #110. One real finding, filed privately as GHSA-xp54-2hxc-w78q (High, triage).

Strict-norm channel. The project's SECURITY.md forbids public vulnerability issues and points to GitHub private vulnerability reporting, which is enabled. The report went through PVR and was accepted into triage on the first attempt, with the vulnerabilities array (the viseron rule holds). The post withholds detail at class level until the advisory resolves.

The finding. Desktop-loopback-inversion: a local Browser Bridge daemon that binds neither who may call it nor which host the request claims, driving privileged browser actions against a site where the operator is authenticated. No scanner rule reported it — it is the absence of a check on an otherwise-working channel. Confirmed with a server-side exploit primitive against the shipped daemon plus a read of the extension source. Graded High not Critical on an honest precondition (the bridge must be actively running), and the fix was written before it was named — narrow, verified not to break the tool's own two legitimate clients.

Curation. 26 findings at medium+, every scanner hit dismissed: 8 SQL identifier FPs (5 high), 8 mutable-action-tag flood, two sha1 dedup ids, two local/dev urllib calls, a loopback health-check react hit, a py3.7 compat rule. verdicts.json validated (exit 0) and copied to corpus/.

• new post (withheld, class level)
• index: new row (private), counts 109 → 110
• scan log: new prose bullet, count 109 → 110
• corpus verdicts row

🤖 Generated with Claude Code