Red Hat Bugzilla – Bug 1149945
CVE-2014-6439 Elasticsearch: CSRF via insecure CORS default configuration
Last modified: 2015-10-23 11:07:59 EDT
It was discovered that the default configuration for cross-origin resource sharing (CORS) exposed a cross-site request forgery (CSRF) vulnerability. A remote attacker could use this flaw by providing a sepecially crafted url to a user, allowing the attacker to send requests to Elasticsearch instances on the users local network leading to data loss or compromise of these instances.
Upstream Fix: https://github.com/elasticsearch/elasticsearch/commit/bd0eb32d9c3c3f5b6e5f8630c859cd04bdcd4e06
Upstream Issue: https://github.com/elasticsearch/elasticsearch/issues/7151
Victims Record: https://github.com/victims/victims-cve-db/blob/master/database/java/2014/6439.yaml
Updating the severity, for Sam 1.x elasticsearch only listens on localhost, thus local access is required. For Satellite 6.x the installation process should include firewalling it to trusted local users only. As such this only scores 3.3 instead of 5.8 on the CVSS2 scoring.
Statement: This issue affects the versions of elasticsearch as shipped with Red Hat Satellite 6.x and Subscription Asset Manager 1.x. Red Hat Product Security has rated this issue as having Low security impact. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.
Mitigation: As provided at http://www.elasticsearch.org/community/security/, Users should either set "http.cors.enabled" to false, or set "http.cors.allow-origin" to the value of the server that should be allowed access, such as localhost or a server hosting Kibana. Disabling CORS entirely with the former setting is more secure, but may not be suitable for all use cases. For Satellite 6.x and Sam 1.x you can simply firewall elasticsearch to trusted users only (e.g. root, katello, foreman). For instructions on this please see: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html-single/Installation_Guide/index.html#sect-Red_Hat_Satellite-Installation_Guide-Red_Hat_Satellite_Installation-Configuring_Red_Hat_Satellite_Manually
I just merged the two Mitigations in comment 1 and comment 9 - marking them private.