Skip to content
This repository has been archived by the owner on May 2, 2019. It is now read-only.

Download compiler and library using HTTPS #397

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

thanatos
Copy link

@thanatos thanatos commented Jun 7, 2018

This reverts commit fb3f4b0.

That commit changed the download of the compiler and library to be done over plain, unencrypted HTTP.

This caused a Node Security Advisory, which states:

Affected versions of closure-util insecurely download an executable over an unencrypted HTTP connection.

In scenarios where an attacker has a privileged network position, it is possible to intercept the response and replace the executable with a malicious one, resulting in code execution on the system running closure-util.

The original change from HTTPS to HTTP was done due to some users reporting that their corporate networks were blocking or failing to download over HTTPS. While this is unfortunate, trading the security of every user of openlayers for a few users with poorly configured networks is not a good balance. This reverts the commit, to ensure that it is not possible for an attacker to compromise the
machine downloading OpenLayers for the majority of users.

For those few who need it, it is still possible to fork this repository and apply the patch to use HTTP, as ill-advised as that would be. It is also possible for them to pin to the version of OpenLayers that contains the above vulnerability.

This reverts commit fb3f4b0.

That commit changed the download of the compiler and library to be done over
plain, unencrypted HTTP.

This caused a Node Security Advisory[1], which states:

	Affected versions of closure-util insecurely download an executable over an
	unencrypted HTTP connection.

	In scenarios where an attacker has a privileged network position, it is
	possible to intercept the response and replace the executable with a
	malicious one, resulting in code execution on the system running
	closure-util.

The original change from HTTPS to HTTP was done due to some users reporting
that their corporate networks were blocking or failing to download over HTTPS.
While this is unfortunate, trading the security of every user of openlayers for
a few users with poorly configured networks is not a good balance. This reverts
the commit, to ensure that it is not possible for an attacker to compromise the
machine downloading OpenLayers for the majority of users.

For those few who need it, it is still possible to fork this repository and
apply the patch to use HTTP, as ill-advised as that would be. It is also
possible for them to pin to the version of OpenLayers that contains the above
vulnerability.

[1]: https://nodesecurity.io/advisories/165
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant