CVE-2016-10622: Insecure Download of Executable in nodeschnaps

nodeschnaps Updated 02 Oct 2025

Summary

18/02/2019
Yes i
High
Not published

CVE-2016-10622: nodeschnaps downloads resources over HTTP. Affects nodeschnaps versions < 1.0.3. Fixed in 1.0.3. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

nodeschnaps is an npm package that allows users to download and manage resources. It is commonly used in Node.js applications to simplify the process of fetching and organizing files. However, versions of nodeschnaps prior to 1.0.3 are vulnerable to an insecure download of 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, potentially leading to code execution on the system running nodeschnaps.

Vulnerability Detail

The vulnerability in nodeschnaps arises from the insecure download of an executable over HTTP. This can be exploited by an attacker who has control over the network traffic between the user and the resource being downloaded. By intercepting the response and replacing the executable with a malicious one, the attacker can execute arbitrary code on the system running nodeschnaps. This can lead to various security risks, including unauthorized access, data theft, and system compromise.

How To Fix

Minimum fixed version

1.0.3

This is the first release that contains the fix.

npm install nodeschnaps@1.0.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If updating nodeschnaps is not immediately feasible, a temporary workaround is to manually download the executable from a trusted source and verify its integrity using cryptographic checksums or digital signatures. By bypassing the insecure download mechanism in nodeschnaps, this workaround reduces the risk of downloading a tampered executable. However, it is important to note that this is only a temporary solution and updating to the latest version of nodeschnaps is still strongly recommended.

Conclusion

In conclusion, nodeschnaps versions prior to 1.0.3 are vulnerable to an insecure download of an executable over HTTP. This can be exploited by attackers to replace the executable with a malicious one, potentially leading to code execution on the system. It is crucial to update nodeschnaps to the latest version to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for nodeschnaps →

Share this vulnerability

FAQ

nodeschnaps is an npm package used for downloading and managing resources in Node.js applications.

The vulnerability allows an attacker to replace the downloaded executable with a malicious one, potentially leading to code execution on the system running nodeschnaps.

To fix this vulnerability, update nodeschnaps to version 1.0.3 or later.

A temporary workaround is to manually download the executable from a trusted source and verify its integrity.

Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability.

How To Fix

Minimum fixed version

1.0.3

This is the first release that contains the fix.

npm install nodeschnaps@1.0.3

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback