Security harden installer to prevent installation on an inititially empty settings.php from leaking database credentials

Created on 26 June 2012, about 12 years ago
Updated 11 July 2023, about 1 year ago

To reproduce:
- Install drupal 8.x but create the settings.php using `touch settings.php` instead of copying the example.
- Enter database connection details.
- Watch it break.

Result:
The database array is written to the file without enclosing <?php tags, causing the array to echo to the browser at the top of every page and may pose an additional security risk.

(sorry if this is a dupe; I looked around a bit and couldn't find another)

✨ Feature request
Status

Postponed: needs info

Version

9.5

Component
InstallΒ  β†’

Last updated 2 days ago

No maintainer
Created by

πŸ‡¨πŸ‡¦Canada Robin Monks

Live updates comments and jobs are added and updated live.
  • Security improvements

    It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024