CVE-2016-10688: Insecure Download of Executable in haxe3

haxe3 Updated 02 Oct 2025

Summary

17/08/2018
No i
High
Not published

CVE-2016-10688: Downloads Resources over HTTP in haxe3. Affected versions are not published. 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

haxe3 is an npm package that provides a toolkit for cross-platform development. It allows developers to write code in the Haxe programming language and compile it to various target platforms. The package is widely used and offers a range of features and functionalities for building applications. However, haxe3 is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in haxe3 arises from the insecure download of an executable file over an unencrypted HTTP connection. This means that when haxe3 attempts to download a resource, an attacker with a privileged network position can intercept the response and replace the executable with a malicious one. If the user runs the compromised executable, it could result in code execution on the system running haxe3. This vulnerability poses a significant risk, particularly in scenarios where an attacker can manipulate network traffic.

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

Given the lack of a patch, the only viable workaround is to avoid using haxe3 and choose an alternative package. This will help mitigate the risk associated with the insecure download of executables over unencrypted connections.

Conclusion

haxe3 is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. Despite active maintenance on the package, no patch has been released for this vulnerability, indicating that the package author has accepted the risk and is unlikely to address it in the future. The best course of action is to avoid using haxe3 and opt for an alternative package. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for haxe3 →

Share this vulnerability

FAQ

haxe3 is an npm package that provides a toolkit for cross-platform development. It allows developers to write code in the Haxe programming language and compile it to various target platforms.

The vulnerability in haxe3 involves the insecure download of an executable over an unencrypted HTTP connection. This allows an attacker to intercept the response and replace the executable with a malicious one, potentially leading to code execution on the system running haxe3.

No, there is currently no patch available for this vulnerability. The package author has not addressed this issue for several years, indicating that it is unlikely to be patched in the future.

The best mitigation is to avoid using haxe3 and opt for an alternative package. If haxe3 is already installed on a private network, ensure that it is not connected to a public network to reduce the risk of exploitation.

The only viable workaround is to avoid using haxe3 and choose an alternative package. This will help mitigate the risk associated with the insecure download of executables over unencrypted connections.

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