CVE-2016-10653: Insecure Download of Executable in xd-testing

xd-testing Updated 02 Oct 2025

Summary

18/02/2019
No i
High
8.1

CVE-2016-10653: xd-testing Downloads Resources over HTTP. Affects xd-testing versions < 1.0.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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The xd-testing package is an npm package used for testing purposes. It provides functionality for executing tests and validating results. The package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. This means that when the package downloads the executable, an attacker with a privileged network position can intercept the response and replace the executable with a malicious one. This can lead to code execution on the system running xd-testing if the malicious executable is executed.

Vulnerability Detail

The vulnerability in xd-testing arises from the insecure download of an executable over an unencrypted HTTP connection. This allows an attacker with a privileged network position to intercept the response and replace the executable with a malicious one. The impact of this vulnerability is that an attacker can execute arbitrary code on the system running xd-testing. This can lead to various malicious activities, such as data theft, system compromise, or unauthorized access. The vulnerability has a high severity rating and is classified under CWE-311.

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 uninstall the xd-testing package and use an alternative package for testing purposes. This can help mitigate the risk of exploitation through the insecure download of an executable.

Conclusion

The xd-testing package is vulnerable to an insecure download of an executable, which can lead to code execution on the system running the package. It is recommended to uninstall the package and use an alternative for testing purposes. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for xd-testing →

Share this vulnerability

FAQ

The impact of this vulnerability is that an attacker can execute arbitrary code on the system running xd-testing. This can lead to various malicious activities, such as data theft, system compromise, or unauthorized access.

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

The best mitigation is to avoid using the xd-testing package and opt for an alternative package if possible. If the package is already installed, it is recommended to uninstall it, especially when connected to a public network.

The risk of exploitation on a private network is limited to those who have compromised the network or have privileged access to the ISP.

This vulnerability has a high severity rating.

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