fix shell command built from environment values

[odaysec]

analytics-next/packages/browser/scripts/vendor/run.js

Lines 6 to 12 in 80ef0be

	const { execSync } = require('node:child_process')
	const path = require('node:path')
	const { createTSFromJSLib } = require('./helpers')
	// build tsub.js with webpack
	const configPath = path.join(__dirname, 'webpack.config.vendor.js')
	execSync(`yarn webpack --config ${configPath}`, { stdio: 'inherit' })

Fix the issue will replace the use of execSync with execFileSync and pass the command arguments separately. This approach avoids shell interpretation of the dynamically constructed command string. Specifically:

1. Replace the dynamic command string `yarn webpack --config ${configPath}` with the command yarn and arguments ['webpack', '--config', configPath].
2. Update the execSync call to use execFileSync with the new command and arguments.

This change ensures that the configPath value is treated as a literal argument and not subject to shell interpretation.

---

References

• Command Injection
• CWE-78
• CWE-88

[changeset-bot]

⚠️ No Changeset found

Latest commit: ce0b3aa

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR