CVE-2016-5408

Stack-based buffer overflow in the munge_other_line function in cachemgr.cgi in the squid package before 3.1.23-16.el6_8.6 in Red Hat Enterprise Linux 6 allows remote attackers to execute arbitrary code via unspecified vectors. NOTE: this vulnerability exists because of an incorrect fix for CVE-2016-4051.

CVE-2016-5419

curl and libcurl before 7.50.1 do not prevent TLS session resumption when the client certificate has changed, which allows remote attackers to bypass intended restrictions by resuming a session.

CVE-2016-5420

curl and libcurl before 7.50.1 do not check the client certificate when choosing the TLS connection to reuse, which might allow remote attackers to hijack the authentication of the connection by leveraging a previously created connection with a different client certificate.

CVE-2016-5421

Use-after-free vulnerability in libcurl before 7.50.1 allows attackers to control which connection is used or possibly have unspecified other impact via unknown vectors.

CVE-2016-6597

Sophos EAS Proxy before 6.2.0 for Sophos Mobile Control, when Lotus Traveler is enabled, allows remote attackers to access arbitrary web-resources from the backend mail system via a request for the resource, aka an Open Reverse Proxy vulnerability.

OAuth2 Client- Moderately Critical – Cross Site Request Forgery – SA-CONTRIB-2016-044

Description

This module provides an OAuth2 client.

The module does not check the validity of the state parameter, during server-side flow, before getting a token. This may allow a malicious user to feed a fake access_token to another user, and subsequently provide him fake data from the server. This page explains it in more details: http://www.twobotechnologies.com/blog/2014/02/importance-of-state-in-oau…

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • OAuth2 Client 7.x-1.x versions prior to 7.x-1.5.

Drupal core is not affected. If you do not use the contributed OAuth2 Client module, there is nothing you need to do.

Solution

Install the latest version:

Also see the OAuth2 Client project page.

Reported by

Fixed by

Coordinated by

Contact and More Information

The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

Piwik – Moderately Critical – Cross Site Scripting – SA-CONTRIB-2016-043

Description

This module enables you to add integration with Piwik statistics service.
The module allows admin users to enter custom JavaScript snippets to add advanced tracking functionality. The permission required to enter this JavaScript was not marked as restricted.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission “Administer Piwik”.

For greater flexibility a new feature has been added to the module to implement the new permission “Add JavaScript snippets” that can be assigned to users who are allowed to add JS code snippets into your web site.

If you have granted the Administer Google Analytics to non trusted users, please check your settings to make sure all javascript entered is valid.

CVE identifier(s) issued

  • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

Versions affected

  • Piwik 7.x-2.x versions prior to 7.x-2.9.
  • Piwik 8.x-2.x versions prior to 8.x-1.1.

Drupal core is not affected. If you do not use the contributed Piwik Web Analytics module, there is nothing you need to do.

Solution

Install the latest version:

  • If you use the Piwik module for Drupal 7.x, upgrade to Piwik 7.x-2.9
  • If you use the Piwik module for Drupal 8.x, upgrade to Piwik 8.x-1.1
  • Also see the Piwik Web Analytics project page.

    Reported by

    Fixed by

    Coordinated by

    Contact and More Information

    The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

    Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

    Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

    Drupal version: 

    Google Analytics – Moderately Critical – Cross Site Scripting – SA-CONTRIB-2016-042

    Description

    This module enables you to add integration with Google Analytics statistics service.
    The module allows admin users to enter custom JavaScript snippets to add advanced tracking functionality. The permission required to enter this JavaScript was not marked as restricted.

    This vulnerability is mitigated by the fact that an attacker must have a role with the permission “Administer Google Analytics”.

    For greater flexibility a new feature has been added to the module to implement the new permission “Add JavaScript snippets” that can be assigned to users who are allowed to add JS code snippets into your web site.

    If you have granted the Administer Google Analytics to non trusted users, please check your settings to make sure all javascript entered is valid.

    CVE identifier(s) issued

    • A CVE identifier will be requested, and added upon issuance, in accordance with Drupal Security Team processes.

    Versions affected

  • Google Analytics 7.x-2.x versions prior to 7.x-2.3.
  • Google Analytics 8.x-2.x versions prior to 8.x-2.1.
  • Drupal core is not affected. If you do not use the contributed Google Analytics module, there is nothing you need to do.

    Solution

    Install the latest version:

  • If you use the Google Analytics module for Drupal 7.x, upgrade to Google Analytics 7.x-2.3
  • If you use the Google Analytics module for Drupal 8.x, upgrade to Google Analytics 8.x-2.1
  • Also see the Google Analytics project page.

    Reported by

    Fixed by

    Coordinated by

    Contact and More Information

    The Drupal security team can be reached at security at drupal.org or via the contact form at https://www.drupal.org/contact.

    Learn more about the Drupal Security team and their policies, writing secure code for Drupal, and securing your site.

    Follow the Drupal Security Team on Twitter at https://twitter.com/drupalsecurity

    Drupal version: