CVE-2016-10676: Insecure Download of Executable in rs-brightcove

rs-brightcove Updated 02 Oct 2025

Summary

18/02/2019
No i
High
Not published

CVE-2016-10676: Downloads Resources over HTTP in rs-brightcove. Affects rs-brightcove versions < 0.0.2. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The rs-brightcove package is an npm package used for downloading resources from the Brightcove video platform. It provides functionality for interacting with the Brightcove API and managing video content. However, this package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in rs-brightcove arises from the insecure download of an executable over an unencrypted HTTP connection. This means that if an attacker has a privileged network position, they can intercept the response and replace the executable with a malicious one. This can lead to code execution on the system running rs-brightcove. The risk of exploitation is higher when connected to a public network, but even on a private network, attackers with compromised network access or privileged ISP access can exploit this vulnerability.

How To Fix

No fixed version is published for this vulnerability.

Currently, there is no patch available for this vulnerability. The best mitigation is to avoid using the rs-brightcove package and opt for an alternative package if possible. If the package is already installed on a private network, it is recommended to ensure that it is not connected to a public network. This reduces the risk of exploitation by limiting access to the package.

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 only workaround is to avoid using the rs-brightcove package and choose a different package for downloading resources from the Brightcove video platform.

Conclusion

The rs-brightcove package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. To mitigate the risk, it is recommended to avoid using this package and choose an alternative. There is currently no patch available for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for rs-brightcove →

Share this vulnerability

FAQ

The impact of this vulnerability is that an attacker can replace the downloaded executable with a malicious one, leading to code execution on the system running rs-brightcove.

This vulnerability can be exploited remotely if the attacker has a privileged network position or privileged ISP access.

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

To reduce the risk of exploitation, it is recommended to avoid using the rs-brightcove package and choose an alternative package. Additionally, ensure that the package is not installed while connected to a public network.

This vulnerability can be exploited by attackers with a privileged network position or privileged ISP access, such as Nation State Actors or Rogue ISP Employees.

How To Fix

No fixed version is published for this vulnerability.

Currently, there is no patch available for this vulnerability. The best mitigation is to avoid using the rs-brightcove package and opt for an alternative package if possible. If the package is already installed on a private network, it is recommended to ensure that it is not connected to a public network. This reduces the risk of exploitation by limiting access to the package.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.