CVE-2016-10649: frames-compiler - Insecure Download of Executable

frames-compiler Updated 02 Oct 2025

Summary

01/09/2020
No i
High
8.1

CVE-2016-10649: frames-compiler downloads Resources over HTTP. Affects frames-compiler versions >= 0.0.0. 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 frames-compiler package is an npm package used for compiling frames, which are a type of data structure used in programming. It is commonly used in web development projects. The package allows developers to compile frames into executable code. However, the package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in frames-compiler 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 frames-compiler. 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, a workaround for this vulnerability is to manually download the executable from a trusted source and replace the insecurely downloaded executable. This can be done by following these steps:

  1. Identify the location of the insecurely downloaded executable.
  2. Download the correct executable from a trusted source.
  3. Replace the insecure executable with the downloaded one.
  4. Verify the integrity of the replaced executable to ensure it has not been tampered with.

Conclusion

The frames-compiler package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. This can lead to code execution on the system running frames-compiler. Currently, there is no patch available for this vulnerability, so it is recommended to avoid using the package and consider alternative solutions. Regularly checking for updates and patches is important to ensure the security of the software.

See every vulnerability recorded for frames-compiler →

Share this vulnerability

FAQ

frames-compiler is an npm package used for compiling frames, which are a type of data structure used in programming. It is commonly used in web development projects.

The vulnerability in frames-compiler is an insecure download of an executable over an unencrypted HTTP connection. This allows an attacker to replace the executable with a malicious one, potentially leading to code execution on the system running frames-compiler.

This vulnerability has a high severity rating.

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

To mitigate the risk of exploitation, it is recommended to avoid using the frames-compiler package and use an alternative package if possible. If the package is already installed on a private network, ensure that it is not connected to a public network.

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