CVE-2016-10573: Insecure Download of Executable in baryton-saxophone
Summary
CVE-2016-10573: Downloads Resources over HTTP in baryton-saxophone. Affects baryton-saxophone versions < 3.0.1. Fixed in 3.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
baryton-saxophone is an npm package that provides functionality related to baryton saxophones. It allows users to interact with and manipulate baryton saxophone resources. However, the package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.
Vulnerability Detail
The affected versions of baryton-saxophone 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, code execution on the system running baryton-saxophone is possible.
How To Fix
Minimum fixed version
3.0.1
This is the first release that contains the fix.
npm install baryton-saxophone@3.0.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In summary, baryton-saxophone is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. To mitigate this vulnerability, it is recommended to update to version 3.0.1 or later. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for baryton-saxophone →
FAQ
baryton-saxophone is an npm package that provides functionality related to baryton saxophones.
The vulnerability allows an attacker to replace the downloaded executable with a malicious one, potentially leading to code execution on the system running baryton-saxophone.
You can fix this vulnerability by updating to version 3.0.1 or later of baryton-saxophone.
No workaround is mentioned for this vulnerability.
You can find more information about this vulnerability in the GitHub advisory database.
