Drupal : fuite d'informations — corrigée en 3.0.2, 2.1.2

1. Vérifier si vous êtes concerné

   Versions ou systèmes touchés :

   <2.1.2 || >=3.0.0 <3.0.2

   drush status --field=drupal-version
   composer show drupal/core

2. Corriger

   Versions corrigées : 3.0.2, 2.1.2.

   Mettre à jour le cœur ou le module concerné avec Composer, appliquer les mises à jour de base, vider les caches, sur chaque site.

   composer update "drupal/core-*" --with-all-dependencies
   composer update drupal/<module> --with-all-dependencies
   drush updatedb -y && drush cache:rebuild

3. En attendant le correctif

   Désactiver le module concerné (drush pm:uninstall <module>) si le correctif ne peut pas passer tout de suite, ou retirer la permission vulnérable aux rôles non administrateurs.

4. Contrôler

   drush status --field=drupal-version et composer show drupal/<module> doivent afficher la version corrigée.

   Rapport de statut Drupal (/admin/reports/status) sans alerte de sécurité.

Commandes indicatives (Debian ou Ubuntu) : à adapter à chaque serveur, après sauvegarde.

This module allows for direct viewing of a file with the URL alias. In some cases, files may be served with the HTTP header Cache-Control: public when they should be uncacheable. This can lead to some users getting cached versions of files with information they should not be able to access. This vulnerability is mitigated by the following: - Drupal must be configured to handle non-public files using a custom or contributed module providing an additional file scheme. - An attacker must know to request a file that has previously been requested by a more-privileged user, and that file must still be cached. Solution : Install the latest version: - If you use the media_alias_display module 3.0.x, upgrade to 3.0.2 - If you use the media_alias_display module 2.1.x, upgrade to 2.1.2