CVE-2018-16462: Command Injection in apex-publish-static-files
Summary
CVE-2018-16462: Command Injection in apex-publish-static-files. Affects apex-publish-static-files versions < 2.0.1. Fixed in 2.0.1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The apex-publish-static-files package is an npm package used for publishing static files in Apex applications. It provides a publish method that allows users to specify a connectString option for connecting to a database. This package is vulnerable to command injection if user input is directly passed into the connectString option.
Vulnerability Detail
The vulnerability in apex-publish-static-files allows an attacker to execute arbitrary commands by injecting malicious input into the connectString option. This can lead to unauthorized access, data leakage, and potential remote code execution. The vulnerability has a severity level of CRITICAL and is classified under CWE-77.
How To Fix
Minimum fixed version
2.0.1
This is the first release that contains the fix.
npm install apex-publish-static-files@2.0.1
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. Updating to the fixed version is the recommended solution.
Conclusion
The apex-publish-static-files package is vulnerable to command injection, which can lead to serious security risks. It is crucial to update to version 2.0.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for apex-publish-static-files →
FAQ
This vulnerability allows an attacker to execute arbitrary commands, potentially leading to unauthorized access, data leakage, and remote code execution.
You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file and it will alert you in real-time.
Yes, updating to version 2.0.1 or later of the apex-publish-static-files package fixes this vulnerability.
There are no known exploits for this vulnerability at the moment.
You can find more information about this vulnerability in the GitHub Advisory Database at https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2018/11/GHSA-9jm3-5835-537m/GHSA-9jm3-5835-537m.json
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.