CVE-2016-10598: Insecure Download of Executable in arrayfire-js

arrayfire-js Updated 02 Oct 2025

Summary

18/02/2019
No i
High
Not published

CVE-2016-10598: arrayfire-js downloads Resources over HTTP. Affects arrayfire-js versions < 0.21.4. 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 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

arrayfire-js is an npm package that provides a JavaScript interface to the ArrayFire library, which is used for high-performance computing. It allows developers to leverage the power of GPUs and other accelerators for numerical computations. However, versions of arrayfire-js prior to 0.21.4 are vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in arrayfire-js arises from the insecure download of an executable file. When the package is installed, it attempts to download a resource over HTTP without encryption. This poses a risk in scenarios where an attacker has a privileged network position. They can intercept the response and replace the executable with a malicious one, leading to code execution on the system running arrayfire-js. This vulnerability has a high severity rating (CWE-311) and can be exploited by attackers who have compromised the network or have 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 the arrayfire-js package. If you must use it, take precautions such as installing it only on a private network and ensuring the network is secure from unauthorized access.

Conclusion

The arrayfire-js package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. Currently, there is no patch available, and the best mitigation is to avoid using the package. If you must use it, take precautions to install it only on a private network and ensure the network is secure from unauthorized access. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for arrayfire-js →

Share this vulnerability

FAQ

arrayfire-js is an npm package that provides a JavaScript interface to the ArrayFire library, enabling high-performance computing using GPUs and other accelerators.

The vulnerability allows an attacker with a privileged network position to replace the downloaded executable with a malicious one, potentially leading to code execution on the system running arrayfire-js.

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

To mitigate the risk, it is recommended to avoid using the arrayfire-js package and consider using an alternative package. If you must use it, ensure it is not installed while connected to a public network and take measures to secure your private network from unauthorized access.

This vulnerability can be exploited by attackers who have compromised the network or have privileged access to the ISP, such as nation-state actors or rogue ISP employees.

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