CVE-2017-16040: Insecure Download of Executable in gfe-sass

gfe-sass Updated 02 Oct 2025

Summary

01/09/2020
No i
High
8.1

CVE-2017-16040: gfe-sass downloads Resources over HTTP. Affects gfe-sass 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 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 gfe-sass package is an npm package used for compiling Sass files. It allows developers to preprocess Sass code into CSS. The package is commonly used in web development projects to streamline the styling process. However, the package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in gfe-sass arises from the insecure download of an executable file. When the package is installed, it attempts to download an executable from a remote server using an unencrypted HTTP connection. This poses a security risk as an attacker with a privileged network position can intercept the response and replace the executable with a malicious one. If successful, this could lead to code execution on the system running gfe-sass. The vulnerability is rated as HIGH severity according to the Common Vulnerability Scoring System (CVSS).

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 gfe-sass package and use an alternative package for Sass compilation. This can be achieved by running the following command in the terminal:

npm uninstall gfe-sass

Conclusion

The gfe-sass package is vulnerable to an insecure download of an executable over an unencrypted HTTP connection. This can potentially lead to code execution on the system. To mitigate the risk, it is advised to uninstall the package and use an alternative solution for Sass compilation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for gfe-sass →

Share this vulnerability

FAQ

gfe-sass is an npm package used for compiling Sass files into CSS. It simplifies the process of styling web applications.

The vulnerability in gfe-sass is related to the insecure download of an executable over an unencrypted HTTP connection. This can allow an attacker to replace the executable with a malicious one, potentially leading to code execution on the system.

The vulnerability is rated as HIGH severity according to the Common Vulnerability Scoring System (CVSS).

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

To mitigate the risk of exploitation, it is recommended to avoid using the gfe-sass package and uninstall it if already installed. Additionally, ensure that the package is not installed while 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