[Issue] Fix PHP 8.5: KEY_MYSQL_SSL_VERIFY hardcoded as 1014 collides with ren…

[m2-assistant]

This issue is automatically created based on existing pull request: #40849: Fix PHP 8.5: KEY_MYSQL_SSL_VERIFY hardcoded as 1014 collides with ren…

---

…amed Pdo\Mysql constant

PHP 8.5 removed ATTR_SERVER_PUBLIC_KEY, shifting all Pdo\Mysql constant values down by one. KEY_MYSQL_SSL_VERIFY was hardcoded as 1014 (a legacy workaround for PHP 7.1.3 support) which now maps to ATTR_LOCAL_INFILE_DIRECTORY instead of ATTR_SSL_VERIFY_SERVER_CERT, causing every Magento 2.4.9 installation on PHP 8.5 to crash on boot with an open_basedir error.

Apply the same PHP_VERSION_ID >= 80400 pattern already used for KEY_MYSQL_SSL_KEY, KEY_MYSQL_SSL_CERT and KEY_MYSQL_SSL_CA.

Description (*)

PHP 8.5 removed Pdo\Mysql::ATTR_SERVER_PUBLIC_KEY, shifting all constant integer values down by one. KEY_MYSQL_SSL_VERIFY was hardcoded as 1014 (legacy workaround for PHP 7.1.3). On PHP 8.5, 1014 is now ATTR_LOCAL_INFILE_DIRECTORY which expects a path — passing false crashes every installation on boot with an open_basedir PDOException.

Applies the same PHP_VERSION_ID >= 80400 pattern already used for KEY_MYSQL_SSL_KEY, KEY_MYSQL_SSL_CERT and KEY_MYSQL_SSL_CA.

Related Pull Requests

Manual testing scenarios (*)

1. Fresh install Magento 2.4.9 on PHP 8.5 with open_basedir — crashes without fix
2. Apply fix, reinstall — boots successfully
3. Check env.php: driver_options contains 1013 => false (correct) instead of 1014 => false

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-17317 is successfully created for this GitHub issue.

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @shlrkb,

Thank you the report and your collaboration!

In order to reproduce the issue, we have followed the below step:

php -d open_basedir="/path/to/magento:/tmp" bin/magento <failing_command>

And we are getting the below output:

lib/internal/Magento/Framework/Filesystem/DirectoryList.php on line 104

Warning: realpath(): open_basedir restriction in effect. File(/private/var/folders/rn/9hffm2_d0fz2jhnys9m6_53h0000gq/T) is not within the allowed path(s): (/var/www/magento2:/tmp) in /lib/internal/Magento/Framework/Filesystem/DirectoryList.php on line 104
PHP Fatal error:  Uncaught TypeError: str_replace(): Argument #3 ($subject) must be of type array|string, false given in /lib/internal/Magento/Framework/Filesystem/DirectoryList.php:137
Stack trace:
#0 /lib/internal/Magento/Framework/Filesystem/DirectoryList.php(137): str_replace('\\', '/', false)
#1 /lib/internal/Magento/Framework/Filesystem/DirectoryList.php(117): Magento\Framework\Filesystem\DirectoryList->normalizePath(false)
#2 /lib/internal/Magento/Framework/App/Filesystem/DirectoryList.php(193): Magento\Framework\Filesystem\DirectoryList->__construct('/opt/homebrew/v...', Array)
#3 /lib/internal/Magento/Framework/App/Bootstrap.php(172): Magento\Framework\App\Filesystem\DirectoryList->__construct('/opt/homebrew/v...', Array)
#4 /lib/internal/Magento/Framework/App/Bootstrap.php(139): Magento\Framework\App\Bootstrap::createFilesystemDirectoryList('/opt/homebrew/v...', Array)
#5 /app/bootstrap.php(35): Magento\Framework\App\Bootstrap::populateAutoloader('/opt/homebrew/v...', Array)
#6 /bin/magento(14): require('/opt/homebrew/v...')
#7 {main}
  thrown in /lib/internal/Magento/Framework/Filesystem/DirectoryList.php on line 137

Fatal error: Uncaught TypeError: str_replace(): Argument #3 ($subject) must be of type array|string, false given in /lib/internal/Magento/Framework/Filesystem/DirectoryList.php:137
Stack trace:
#0 /lib/internal/Magento/Framework/Filesystem/DirectoryList.php(137): str_replace('\\', '/', false)
#1 /lib/internal/Magento/Framework/Filesystem/DirectoryList.php(117): Magento\Framework\Filesystem\DirectoryList->normalizePath(false)
#2 /lib/internal/Magento/Framework/App/Filesystem/DirectoryList.php(193): Magento\Framework\Filesystem\DirectoryList->__construct('/opt/homebrew/v...', Array)
#3 /lib/internal/Magento/Framework/App/Bootstrap.php(172): Magento\Framework\App\Filesystem\DirectoryList->__construct('/opt/homebrew/v...', Array)
#4 /lib/internal/Magento/Framework/App/Bootstrap.php(139): Magento\Framework\App\Bootstrap::createFilesystemDirectoryList('/opt/homebrew/v...', Array)
#5 /app/bootstrap.php(35): Magento\Framework\App\Bootstrap::populateAutoloader('/opt/homebrew/v...', Array)
#6 /bin/magento(14): require('/opt/homebrew/v...')
#7 {main}
  thrown in /lib/internal/Magento/Framework/Filesystem/DirectoryList.php on line 137

Hence we are confirming this issue.