You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Security fixes for 2.8.1: credentials sent as headers, stored in history, and an SSRF through a locked server URL #759
Three defects in 2.8.0 that expose credentials or the host's network. They are fixed on main (5a920d4, f6d22b4, da3c841) but ship there only with 2.9's features; 2.8.0 users need them as a patch.
Internal markers sent as headers. The workbench puts plugin configuration into the call's metadata — __bowireMtls__ carries the client's private key, __bowireAwsSigV4__ the AWS secret key. GraphQL, SSE, JSON-RPC, SignalR, WebSocket, Connect/gRPC-Web and MCP copied the whole bag onto the request, so with mTLS or SigV4 auth in the environment those secrets reached the target server as literal headers.
Credentials in history and recordings. History (localStorage) and recordings kept the metadata after the auth helper resolved it: resolved {{secret.*}} values in headers, and the markers above.
SSRF with LockServerUrl. A locked workbench only made the URL field read-only; the endpoints still dialed any ?serverUrl=, so a locked Bowire was an open relay into its host's network (e.g. the cloud metadata endpoint).
What
release/2.8 from v2.8.0 with the three fixes (and the release-script fix for large gh output that the pipeline needs).
Release notes docs/release-notes/v2.8.1.md, also on main for the changelog page.
Tag v2.8.1.
Acceptance criteria
No __bowire* key reaches a target as a header, for any protocol.
History and recordings hold no resolved secret and no credential header value.
With LockServerUrl or AllowedServerUrls, a call to another target is refused with 403.
Auf release/2.8 (ab v2.8.0): bd92ec5 (Release-Skripte, fuer die Pipeline), 6a86ac7 (Marker nicht als Header), 49c0f96 (LockServerUrl serverseitig, AllowedServerUrls), cb6780a (Historie/Aufzeichnungen ohne Zugangsdaten), Notes 18f23a2. Tests auf dem Branch gruen (Core 3757, Integration 750, Plugins, JS 1107). Tag v2.8.1 folgt.
Activity
thomas-stegemann commentedon Sep 30, 2026
Auf release/2.8 (ab v2.8.0): bd92ec5 (Release-Skripte, fuer die Pipeline), 6a86ac7 (Marker nicht als Header), 49c0f96 (LockServerUrl serverseitig, AllowedServerUrls), cb6780a (Historie/Aufzeichnungen ohne Zugangsdaten), Notes 18f23a2. Tests auf dem Branch gruen (Core 3757, Integration 750, Plugins, JS 1107). Tag v2.8.1 folgt.
docs(release): Release-Notes 2.8.1 auch auf main, fuer die Changelog-…
docs(release): Release-Notes 2.8.1 auch auf main, fuer die Changelog-…