CVE-2016-10569: Insecure Download of Executable in embedza
Summary
CVE-2016-10569: Downloads Resources over HTTP in embedza. Affects embedza versions < 1.2.4. Fixed in 1.2.4. 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
embedza is an npm package that allows embedding media resources in text documents. It provides a convenient way to generate HTML code for embedding various types of media, such as YouTube videos, Twitter tweets, and more. This package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.
Vulnerability Detail
The affected versions of embedza insecurely download an executable over an unencrypted HTTP connection. This means that if an attacker has a privileged network position, they can intercept the response and replace the executable with a malicious one. As a result, when the system running embedza executes the downloaded executable, it can lead to code execution with the attacker's malicious code.
How To Fix
Minimum fixed version
1.2.4
This is the first release that contains the fix.
npm install embedza@1.2.4Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In summary, embedza is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. To mitigate this vulnerability, it is crucial to update embedza to version 1.2.4 or later. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for embedza →
FAQ
embedza is an npm package that allows embedding media resources in text documents.
The vulnerability allows an attacker to replace the downloaded executable with a malicious one, leading to code execution on the system running embedza.
You can fix this vulnerability by updating embedza to version 1.2.4 or later.
No, the recommended fix is to update to the latest version of embedza.
You can find more information about this vulnerability in the GitHub Advisory Database.
