chore(deps): update dependency tidewave to v0.9.2 [security] #637
No reviewers
Labels
No labels
bug
duplicate
enhancement
help wanted
high priority
invalid
L
low priority
M
medium priority
needs refinement
optional
question
S
security
technical improvement
UX Improvement
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
local-it/mitgliederverwaltung!637
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/hex-tidewave-vulnerability"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.9.1→0.9.2Host filesystem path disclosure via DNS rebinding
CVE-2026-109823 / EEF-CVE-2026-109823
More information
Details
Summary
An attacker can read the name of filesystem paths of your application present via Tidewave configuration via /tidewave/connect or via the rendered toolbar.
Neither response checks the
Hostheader. A web page that rebinds its own domain to the loopback address can therefore read the tag with a same-origin request, which carries noOriginheader. The paths usually reveal the local username and the project layout.This issue affects tidewave: from 0.8.0 before 0.9.2.
Details
1. Data collection.
Tidewave.tidewave_config_meta/1builds a map withroot(Tidewave.MCP.root()),framework.app_paths(Mix.Project.deps_paths()),wsl_distro, andhost_path. It HTML-escapes the JSON encoding of the map into<meta name="tidewave:config">.2. Exposure.
Tidewave.Router.control_html/1serves the tag onGET /tidewave/connect. For all other routes,Tidewave.call/2registers abefore_sendcallback that injects the tag into everytext/htmlresponse whentoolbar: true.3. Read access.
check_origin/2accepts any request without anOriginheader, and no code validatesHost. After DNS rebinding, the browser sends a same-originGETfrom a loopback peer.Proof of concept
plug Tidewaveon127.0.0.1:4001.GET /tidewave/connectwithHost: attacker.example:4001andSec-Fetch-Site: same-origin, and noOriginheader. This is the request a DNS-rebound page makes.200 OK. Thetidewave:configmeta tag contains the absolute project root and the dependency paths.Impact
A malicious web page that a developer visits while the Phoenix development server runs can learn the developer's username, project location, and dependency layout on disk. This information helps an attacker prepare further attacks against the machine.
Severity
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NReferences
This data is provided by OSV.
Release Notes
tidewave-ai/tidewave_phoenix (tidewave)
v0.9.2Compare Source
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
Pull request closed