CVE-2016-10617: Insecure Download of Executable in box2d-native

box2d-native Updated 02 Oct 2025

Summary

18/02/2019
No i
High
Not published

CVE-2016-10617: Downloads Resources over HTTP in box2d-native. Affects box2d-native versions < 0.0.8. 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

box2d-native is an npm package that provides a native implementation of the Box2D physics engine. It is commonly used in game development and physics simulations. The package allows developers to integrate physics-based interactions into their applications. However, versions of box2d-native prior to 0.0.9 are vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in box2d-native arises from the insecure download of an executable file. When the package is installed, it attempts to download a resource over an unencrypted HTTP connection. This behavior can be exploited by an attacker who has a privileged network position. They can intercept the response and replace the executable with a malicious one. If successful, this could lead to code execution on the system running box2d-native. The impact of this vulnerability is significant, as it allows an attacker to compromise the integrity and security of the system.

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 box2d-native package. Developers should consider using alternative packages that provide similar functionality but do not have this vulnerability. By choosing a different package, the risk of exploitation can be mitigated.

Conclusion

The box2d-native package has a vulnerability that allows an attacker to replace the downloaded executable with a malicious one, potentially leading to code execution on the system. Currently, there is no patch available, so the best course of action is to avoid using the affected package and consider using an alternative. If you have any further questions or need assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for box2d-native →

Share this vulnerability

FAQ

box2d-native is an npm package that provides a native implementation of the Box2D physics engine. It is commonly used in game development and physics simulations.

The vulnerability allows an attacker to intercept and replace the executable file downloaded by box2d-native, potentially leading to code execution on the affected system.

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

To mitigate the risk of exploitation, avoid using the affected package and consider using an alternative package. Additionally, ensure that the package is not installed while connected to a public network.

This vulnerability requires an attacker to have a privileged network position to intercept the download and replace the executable. Therefore, it cannot be exploited remotely unless the 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 →

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