ECHOES-1271 [renovate] Update dependency vite to v7.3.2 [SECURITY]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite (source)	7.3.1 → 7.3.2

---

Vite Vulnerable to Path Traversal in Optimized Deps .map Handling

GHSA-4w7w-66w2-5vf9

More information

Details

Summary

Any files ending with .map even out side the project can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

• explicitly exposes the Vite dev server to the network (using --host or server.host config option)
• have a sensitive content in files ending with .map and the path is predictable

Details

In Vite v7.3.1, the dev server’s handling of .map requests for optimized dependencies resolves file paths and calls readFile without restricting ../ segments in the URL. As a result, it is possible to bypass the server.fs.strict allow list and retrieve .map files located outside the project root, provided they can be parsed as valid source map JSON.

PoC

1. Create a minimal PoC sourcemap outside the project root

   cat > /tmp/poc.map <<'EOF'
   {"version":3,"file":"x.js","sources":[],"names":[],"mappings":""}
   EOF

2. Start the Vite dev server (example)

   pnpm -C playground/fs-serve dev --host 127.0.0.1 --port 18080

3. Confirm that direct /@​fs access is blocked by strict (returns 403)
   
4. Inject ../ segments under the optimized deps .map URL prefix to reach /tmp/poc.map
   

Severity

• CVSS Score: 6.3 / 10 (Medium)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/vitejs/vite/security/advisories/GHSA-4w7w-66w2-5vf9
• https://github.com/vitejs/vite/pull/22161
• https://github.com/vitejs/vite/commit/79f002f2286c03c88c7b74c511c7f9fc6dc46694
• https://github.com/vitejs/vite
• https://github.com/vitejs/vite/releases/tag/v6.4.2
• https://github.com/vitejs/vite/releases/tag/v7.3.2
• https://github.com/vitejs/vite/releases/tag/v8.0.5

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Vite Vulnerable to Arbitrary File Read via Vite Dev Server WebSocket

GHSA-p9ff-h696-f583

More information

Details

Summary

server.fs check was not enforced to the fetchModule method that is exposed in Vite dev server's WebSocket.

Impact

Only apps that match the following conditions are affected:

• explicitly exposes the Vite dev server to the network (using --host or server.host config option)
• WebSocket is not disabled by server.ws: false

Arbitrary files on the server (development machine, CI environment, container, etc.) can be exposed.

Details

If it is possible to connect to the Vite dev server’s WebSocket without an Origin header, an attacker can invoke fetchModule via the custom WebSocket event vite:invoke and combine file://... with ?raw (or ?inline) to retrieve the contents of arbitrary files on the server as a JavaScript string (e.g., export default "...").

The access control enforced in the HTTP request path (such as server.fs.allow) is not applied to this WebSocket-based execution path.

PoC

1. Start the dev server on the target
   Example (used during validation with this repository):

   pnpm -C playground/alias exec vite --host 0.0.0.0 --port 5173

2. Confirm that access is blocked via the HTTP path (example: arbitrary file)

   curl -i 'http://localhost:5173/@​fs/etc/passwd?raw'

   Result: 403 Restricted (outside the allow list)
   

3. Confirm that the same file can be retrieved via the WebSocket path
   By connecting to the HMR WebSocket without an Origin header and sending a vite:invoke request that calls fetchModule with a file://... URL and ?raw, the file contents are returned as a JavaScript module.

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/vitejs/vite/security/advisories/GHSA-p9ff-h696-f583
• https://github.com/vitejs/vite/pull/22159
• https://github.com/vitejs/vite/commit/f02d9fde0b195afe3ea2944414186962fbbe41e0
• https://github.com/vitejs/vite
• https://github.com/vitejs/vite/releases/tag/v6.4.2
• https://github.com/vitejs/vite/releases/tag/v7.3.2
• https://github.com/vitejs/vite/releases/tag/v8.0.5

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Vite: server.fs.deny bypassed with queries

GHSA-v2wj-q39q-566r

More information

Details

Summary

The contents of files that are specified by server.fs.deny can be returned to the browser.

Impact

Only apps that match the following conditions are affected:

• explicitly exposes the Vite dev server to the network (using --host or server.host config option)
• the sensitive file exists in the allowed directories specified by server.fs.allow
• the sensitive file is denied with a pattern that matches a file by server.fs.deny

Details

On the Vite dev server, files that should be blocked by server.fs.deny (e.g., .env, *.crt) can be retrieved with HTTP 200 responses when query parameters such as ?raw, ?import&raw, or ?import&url&inline are appended.

PoC

1. Start the dev server: pnpm exec vite root --host 127.0.0.1 --port 5175 --strictPort
2. Confirm that server.fs.deny is enforced (expect 403): curl -i http://127.0.0.1:5175/src/.env | head -n 20
   
3. Confirm that the same files can be retrieved with query parameters (expect 200):
   

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

References

• https://github.com/vitejs/vite/security/advisories/GHSA-v2wj-q39q-566r
• https://github.com/vitejs/vite/pull/22160
• https://github.com/vitejs/vite/commit/a9a3df299378d9cbc5f069e3536a369f8188c8ff
• https://github.com/vitejs/vite
• https://github.com/vitejs/vite/releases/tag/v7.3.2
• https://github.com/vitejs/vite/releases/tag/v8.0.5

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

vitejs/vite (vite)

v7.3.2

Compare Source

Please refer to CHANGELOG.md for details.

---

Configuration

📅 Schedule: Branch creation - "" in timezone CET, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

• If the PR is green: it means that the dependencies have been update successfully; double check the changelog and merge! When merging don't forget to squash the commit and add prefix the commit message witht the JIRA tickets that has been automatically created.
• If the PR is red: something went wrong; double check the changelog and then either:
  • Fix the issues if the breaking changes are quick to fix or you have the time for it: make sure to add a new commit and not to modify the one from the Renovate
  • If the required changes are too big: create a JIRA ticket and assign it to the FEE squad, finally update the rennovate.json file to ignore the dependency and document the reason why it has been ignored, the Renovate PR can be closed.

To know more about the whole process, check our WebApp dependencies management xtranet page.

[netlify]

✅ Deploy Preview for echoes-react ready!

Name	Link
🔨 Latest commit	05a6c2e
🔍 Latest deploy log	https://app.netlify.com/projects/echoes-react/deploys/69d75243cd725100084e23d6
😎 Deploy Preview	https://deploy-preview-665--echoes-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hashicorp-vault-sonar-prod]

Renovate Jira issue ID: ECHOES-1271

[sonar-review-alpha]

Summary

⚠️ The PR description exceeded the analysis limit and was truncated. The review may not reflect all context.

This PR updates Vite from 7.3.1 to 7.3.2 to address two security vulnerabilities in the dev server:

1. Path traversal via .map requests (GHSA-4w7w-66w2-5vf9, CVSS 6.3): Allows bypassing server.fs.strict restrictions to retrieve .map files outside the project root when the dev server is exposed to the network.

2. Arbitrary file read via WebSocket (GHSA-p9ff-h696-f583): The fetchModule method in the dev server's WebSocket interface does not enforce server.fs checks, potentially exposing arbitrary files on the server if WebSocket is accessible.

Both vulnerabilities require specific conditions—primarily that the Vite dev server is explicitly exposed to the network (via --host or config). This is a straightforward patch update with no breaking changes or additional configuration needed.

What reviewers should know

What changed: Only dependency versions updated in package.json and yarn.lock—no code changes to review.

Scope assessment: Check if your dev server setup matches the vulnerable conditions:

• Is the dev server exposed to the network in any workflows (development, CI, containers)?
• Are WebSockets left enabled by default?
• If either is true, this patch eliminates attack vectors for the conditions you'd actually use.

For review: Verify the lock file integrity and confirm vite 7.3.2 has no unexpected transitive dependency changes (the checksum reflects the expected difference). No functional testing needed—this is a pure security patch.

---

• Generate Walkthrough
• Generate Diagram

🗣️ Give feedback

[sonar-review-alpha]

LGTM! ✅

Clean, minimal security patch — only package.json and yarn.lock are touched, the checksum is updated correctly, and no application code is affected. Safe to merge.

🗣️ Give feedback

[sonarqube-next]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
0 Dependency risks
No data about Coverage
No data about Duplication

See analysis details on SonarQube