CVE-2016-10590: Insecure Download of Executable in cue-sdk-node

cue-sdk-node Updated 02 Oct 2025

Summary

18/02/2019
No i
High
Not published

CVE-2016-10590: Downloads Resources over HTTP in cue-sdk-node. Affects cue-sdk-node versions < 1.2.1. 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 Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

cue-sdk-node is an npm package that provides a Node.js interface for controlling Corsair RGB devices. It allows developers to interact with Corsair's CUE SDK to customize lighting effects and manage device settings. The package is widely used in applications that require RGB lighting control for Corsair devices.

Vulnerability Detail

Affected versions of cue-sdk-node insecurely download an executable over an unencrypted HTTP connection. This means that when the package is installed or updated, it retrieves an executable file from a remote server using HTTP instead of the more secure HTTPS protocol. This poses a security risk because an attacker with privileged network position can intercept the response and replace the executable with a malicious one. If the compromised executable is executed on the system running cue-sdk-node, it can lead to arbitrary code execution. The vulnerability is assigned the identifier CVE-2016-10590 and has a severity rating of HIGH.

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 workaround for this vulnerability is to avoid using cue-sdk-node. If you need RGB lighting control for Corsair devices, consider using a different package that does not have this vulnerability.

Conclusion

In conclusion, cue-sdk-node is vulnerable to an insecure download of an executable, which can lead to arbitrary code execution if a malicious executable is substituted. Currently, there is no patch available for this vulnerability. The best course of action is to avoid using cue-sdk-node and consider alternative packages. If you need further assistance or support in addressing this vulnerability, please contact DevNack.com.

See every vulnerability recorded for cue-sdk-node →

Share this vulnerability

FAQ

cue-sdk-node is an npm package that provides a Node.js interface for controlling Corsair RGB devices.

The impact of this vulnerability is that an attacker with a privileged network position can intercept the download of an executable file and replace it with a malicious one. If the compromised executable is executed on the system running cue-sdk-node, it can lead to arbitrary code execution.

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

To mitigate the risk of exploitation, it is recommended to avoid using cue-sdk-node and choose an alternative package if possible. If you must use cue-sdk-node, ensure that the package is not installed or updated while connected to a public network.

The workaround for this vulnerability is to avoid using cue-sdk-node and opt for a different package that does not have this vulnerability.

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