View online: https://www.drupal.org/psa-2021-11-30
Date: 2021-November-30
Description:
As of November 17, 2021, the Drupal core version 8 series has reached
end-of-life. This means that all releases of Drupal 8 core (with 8.y.x
version numbers) and Drupal contributed project releases that are compatible
with only Drupal 8 will be marked unsupported as they no longer have security
team support.
Drupal 8.0.0 was first released on November 9, 2015. The last version was
released on November 17, 2021.
All Drupal 8 site owners must upgrade to Drupal 9 [1] to receive security
updates and bug fixes. The Drupal Association will also disable testing with
unsupported versions of Drupal.
Security issues that only affect Drupal 8 (and not Drupal 9 or Drupal 7) will
be made public and sites are at risk of having these issues exploited if they
do not upgrade.
.... What about Drupal 7 and Drupal 9?
Contributed projects like themes and modules will still receive security
advisories if they are compatible with either Drupal 7 or 9 and have opted in
to security coverage.
Drupal 7's end-of-life is currently scheduled for November of 2022 [2], and
it will receive security updates until then. Drupal 9's end-of-life is
scheduled for November of 2023. For more information on release schedules,
see the core release cycle overview [3].
[1]
https://www.drupal.org/docs/upgrading-drupal/how-to-prepare-your-drupal-7-o…
[2] https://www.drupal.org/psa-2020-06-24
[3] https://www.drupal.org/core/release-cycle-overview
View online: https://www.drupal.org/sa-contrib-2021-036
Project: SAML SP 2.0 Single Sign On (SSO) - SAML Service Provider [1]
Date: 2021-September-22
Security risk: *Moderately critical* 14∕25
AC:Basic/A:None/CI:Some/II:Some/E:Theoretical/TD:Uncommon [2]
Vulnerability: Multiple vulnerabilities
Description:
This module provides a solution to authenticate visitors using existing SAML
providers.
Certain non-default configurations allow a malicious user to login as any
chosen user.
The vulnerability is mitigated by the module's default settings which require
the options "Either sign SAML assertions" and "x509 certificate".
Solution:
Ensure that the "Either SAML response or SAML assertion must be signed" and
"x509 certificate" options on the dedicated plugin page are both enabled.
Install the latest version:
* If you use the SAML SP 2.0 Single Sign On (SSO) - SAML Service Provider
module for Drupal 8.x or 9.x, upgrade to SAML SP 2.0 Single Sign On (SSO)
- SAML Service Provider 8.x-2.24 [3]
* If you use the SAML SP 2.0 Single Sign On (SSO) - SAML Service Provider
module for Drupal 7.x, upgrade to SAML SP 2.0 Single Sign On (SSO) - SAML
Service Provider 7.x-2.57 [4]
Reported By:
* Cristian 'void' Giustini [5]
Fixed By:
* Cristian 'void' Giustini [6]
* abhay19 [7]
Coordinated By:
* Damien McKenna [8] of the Drupal Security Team
[1] https://www.drupal.org/project/miniorange_saml
[2] https://www.drupal.org/security-team/risk-levels
[3] https://www.drupal.org/project/miniorange_saml/releases/8.x-2.24
[4] https://www.drupal.org/project/miniorange_saml/releases/7.x-2.60
[5] https://www.drupal.org/user/3680969
[6] https://www.drupal.org/user/3680969
[7] https://www.drupal.org/user/3549350
[8] https://www.drupal.org/u/damienmckenna