Snyk Security Database

vite-plus is a The Unified Toolchain for the Web

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the getHtmlFilename function in packages/vite/src/node/server/middlewares/indexHtml.ts, where query strings are not stripped from the URL before the filename is constructed and passed to transformIndexHtml. An attacker who can influence the URL of an HTML request can supply a URL containing query parameters or a protocol-relative path (starting with //), causing the filename passed to transform hooks to be incorrect and potentially allowing unintended resource resolution or URL manipulation in generated script and link tags.

Affected versions of this package are vulnerable to Improper Validation of Integrity Check Value via the seed wheel acquisition logic in src/virtualenv/seed/wheels/acquire.py and pip_invoke.py, where wheels are cached and then passed to pip for installation without verifying their integrity before use. When the --find-links directories used by pip contain multiple wheel files matching a distribution, pip selects among them by filename, allowing a wheel that was placed in the cache directory prior to digest verification to be installed instead of the expected, verified wheel. An attacker who can write to the shared wheel cache directory can substitute a malicious wheel that pip then installs into the new virtual environment.

Affected versions of this package are vulnerable to Out-of-bounds Read in the decodeChunk method of UnsafeChunkDecoder, which resolves back references and copies literal runs through sun.misc.Unsafe without confirming that a back reference lands at or after the start of the output region, or that a literal run near the end of the input lies within the input array. An attacker can read memory outside both arrays into the decompressed result, and crash the JVM, by supplying LZF data whose back reference offset points before the first byte written or whose trailing literal run extends past the end of the compressed input, since Unsafe accesses carry no bounds checking. This requires the application to decompress LZF data from a source it does not control and the Unsafe based decoder to be the one in use.