LoopX
LoopX serve-status permissive CORS policy exposes control-plane state and private Markdown files
Open and provider-neutral, LoopX is a lightweight state kernel and local-first control plane for loop engineering. From version 0.0.1 until 0.4.5, `loopx serve-status` in `loopx/status_server.py` uses `StatusRequestHandler._send_json()` and `do_OPTIONS()` to send `Access-Control-Allow-Origin: *` for unauthenticated responses on predictable loopback ports. A remote attacker can cause an operator who visits attacker-controlled web content to issue cross-origin requests to `GET /status.json`, `GET /review-material?goal_id=...&path=...`, `GET /`, and `POST /control-plane/configure-goal/dry-run`, exposing control-plane state, goal and run information, local absolute paths, private Markdown files below registered goal roots, and dry-run configuration projections. The affected routes do not provide cross-origin writes or arbitrary-file access. This issue is fixed in version 0.4.5.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 0.0.1, < 0.4.5
Fixed in 0.4.5
Mitigation
Upgrade loopx to 0.4.5 or later.
References
- Vendor advisory github.com/loopx-project/loopx/security/adviso…
- Patch github.com/loopx-project/loopx/pull/3137
- Patch github.com/loopx-project/loopx/commit/838720fb…
1 more
- Release notes github.com/loopx-project/loopx/releases/tag/v0…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.