CVE-2016-10582: Insecure Download of Resources in closurecompiler

closurecompiler Updated 02 Oct 2025

Summary

18/02/2019
No i
High
8.1

CVE-2016-10582: closurecompiler downloads Resources over HTTP. Affects closurecompiler versions < 1.6.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 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

closurecompiler is an npm package that provides a JavaScript optimizing compiler. It is commonly used to minify and optimize JavaScript code. The package allows developers to improve the performance and efficiency of their JavaScript applications. However, versions of closurecompiler prior to 1.6.1 are vulnerable to an insecure download of resources over an unencrypted HTTP connection.

Vulnerability Detail

The vulnerability in closurecompiler arises from the insecure download of an executable file 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 could lead to code execution on the system running closurecompiler. 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 →

Conclusion

In conclusion, closurecompiler versions prior to 1.6.1 are vulnerable to an insecure download of resources over an unencrypted HTTP connection. To mitigate this vulnerability, it is crucial to update to version 1.6.1 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for closurecompiler →

Share this vulnerability

FAQ

closurecompiler is an npm package that provides a JavaScript optimizing compiler. It is used to minify and optimize JavaScript code for improved performance and efficiency.

The vulnerability allows an attacker with a privileged network position to intercept and replace the executable downloaded by closurecompiler. This could result in code execution on the system running closurecompiler.

Updating closurecompiler to version 1.6.1 or later ensures that resources are downloaded securely over an encrypted HTTPS connection, reducing the risk of interception and code execution.

No workaround is available for this vulnerability. It is recommended to update to the latest version of closurecompiler.

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