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 s...

Some files viewed through a URL alias may be served with Cache-Control: public when they should not be cached, allowing users to receive files containing information they should not be able to access. This requires Drupal to handle non-public files through an additional file scheme, and the attacker must know to request a file previously requested by a more-privileged user while it remains cached.

Look for drupal/media_alias_display and its version in composer.lock. The advisory lists 2.1.2 and 3.0.2 as fixed versions but gives no affected version ranges. Check whether Drupal uses a custom or contributed module providing an additional file scheme for non-public files, and whether those files can remain cached after a more-privileged user requests them.

The advisory limits exposure to sites using a custom or contributed module that provides an additional file scheme for non-public files. An attacker must know to request a file previously requested by a more-privileged user, and that file must still be cached.

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.