CVE-2016-10608: Insecure Download of Executable in robot-js

robot-js Updated 02 Oct 2025

Summary

18/02/2019
No i
High
7.5

CVE-2016-10608: robot-js downloads Resources over HTTP. Affects robot-js versions < 2.0.0. No fix is published. 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

robot-js is an npm package that provides a bridge between JavaScript and native code, allowing developers to write native addons for Node.js using C++. It is commonly used for tasks that require low-level system access or performance optimization. However, versions of robot-js prior to 2.0.0 are vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in robot-js arises from the insecure download of an executable file. When the package attempts to download a resource, it does so over an unencrypted HTTP connection. This opens up the possibility for an attacker with a privileged network position to intercept the response and replace the executable with a malicious one. If successful, this could lead to code execution on the system running robot-js. The risk of exploitation is particularly high when connected to a public network or when an attacker has compromised the network or has privileged access to the ISP.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As there is no patch available, the recommended workaround is to avoid using robot-js and choose an alternative package. If that is not feasible, extra caution should be exercised when using robot-js on public networks or networks that may be compromised. Regularly monitoring for updates and patches from the package maintainers is also crucial.

Conclusion

The vulnerability in robot-js that allows for the insecure download of an executable poses a significant risk to systems running this package. It is recommended to avoid using robot-js and opt for an alternative package. Regularly monitoring for updates and patches from the package maintainers is crucial to stay informed about any security fixes. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for robot-js →

Share this vulnerability

FAQ

robot-js is an npm package that provides a bridge between JavaScript and native code, allowing developers to write native addons for Node.js using C++.

The vulnerability allows an attacker with a privileged network position to intercept the download of an executable file and replace it with a malicious one. This could lead to code execution on the system running robot-js.

No, currently there is no patch available for this vulnerability.

The best mitigation is to avoid using robot-js and choose an alternative package. If already installed on a private network, ensure it is not used while connected to a public network. Regularly monitor for updates and patches from the package maintainers.

If you suspect exploitation of this vulnerability, it is recommended to disconnect from the network, remove the robot-js package, and seek assistance from a security professional to investigate and remediate the issue.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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