CVE-2016-10635: Insecure Download of Executable in broccoli-closure
Summary
CVE-2016-10635: Downloads Resources over HTTP in broccoli-closure. Affects broccoli-closure versions < 1.3.1. Fixed in 1.3.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
broccoli-closure is an npm package used for building JavaScript applications. It is designed to compile and optimize JavaScript code using the Closure Compiler. The package is widely used in web development projects. However, certain versions of broccoli-closure are vulnerable to an insecure download of an executable file over an unencrypted HTTP connection.
Vulnerability Detail
The affected versions of broccoli-closure insecurely download an executable file over an unencrypted HTTP connection. This vulnerability can be exploited by an attacker with a privileged network position. They can intercept the response and replace the executable with a malicious one. When the system running broccoli-closure executes the downloaded file, it can lead to code execution with the attacker's malicious code.
How To Fix
Minimum fixed version
1.3.1
This is the first release that contains the fix.
npm install broccoli-closure@1.3.1
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
The insecure download of executables in certain versions of broccoli-closure poses a security risk. It is crucial to update to version 1.3.1 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for broccoli-closure →
FAQ
The vulnerability allows an attacker to replace the downloaded executable with a malicious one, leading to code execution on the system running broccoli-closure.
No, this vulnerability requires an attacker to have a privileged network position to intercept the download.
No, only versions prior to 1.3.1 are affected. Updating to version 1.3.1 or later mitigates the vulnerability.
No, the recommended solution is to update to a secure version of broccoli-closure.
You can find more information about this vulnerability in the GitHub Advisory Database.