Homepage

Information Exposure Affecting vitess-19.0 package, versions <19.0.10-r4

Severity

 Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

Exploit Maturity
Proof of Concept

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-VITESS190-9563916
  • published28 Mar 2025
  • disclosed24 Mar 2025
Report a new vulnerability Found a mistake?

Introduced: 24 Mar 2025

NewCVE-2025-30208  (opens in a new tab)
CWE-200  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade Chainguard vitess-19.0 to version 19.0.10-r4 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream vitess-19.0 package and not the vitess-19.0 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

Vite, a provider of frontend development tooling, has a vulnerability in versions prior to 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10. @fs denies access to files outside of Vite serving allow list. Adding ?raw?? or ?import&amp;raw?? to the URL bypasses this limitation and returns the file content if it exists. This bypass exists because trailing separators such as ? are removed in several places, but are not accounted for in query string regexes. The contents of arbitrary files can be returned to the browser. Only apps explicitly exposing the Vite dev server to the network (using --host or server.host config option) are affected. Versions 6.2.3, 6.1.2, 6.0.12, 5.4.15, and 4.5.10 fix the issue.