OS Command Injection in pdf-image

Successful exploitation enables execution of arbitrary OS commands with the privileges of the process using pdf-image. This can result in complete compromise of the confidentiality, integrity, and availability of resources accessible to that process.

Do not pass untrusted or insufficiently validated values as pdfFilePath. Where feasible, replace or locally patch the affected command construction to use child_process.execFile or spawn with a fixed executable and a separately supplied argument array, rather than a shell command string. Restrict the service account running the application to minimum required filesystem, process, and network privileges.

Upgrade to a fixed version if one is made available by the maintainer. If no patched release is available, modify the package or forked code to eliminate shell-based command construction from untrusted input. Replace child_process.exec() with safer process-spawning patterns such as execFile() or spawn() using argument arrays and strict separation of executable and parameters. Ensure pdfFilePath is treated strictly as data, not interpolated into shell command strings, and apply robust allowlisting or escaping appropriate to the execution model.