Magento Version exposure via Setup route with default Nginx Configuration

[SamJUK]

Preconditions and environment

Any Version of Magento using the Nginx sample config

Steps to reproduce

Navigate to https://site.com/setup/

Expected result

Return a 401/403 error, or at very minimum do not expose the exact version of Magento the site is running.

Actual result

We see a lovely page telling us exactly the Magento version is

Additional information

I believe in 2.4, the web based setup was removed. Although the page is still accessible displaying the Magento Version.

Typically those using the default Nginx configuration are less technical / security focused. And they trust the default provided Nginx configure is secure by default. I would argue exposing the exact Magento package version provides no benefit whilst telling potential bad actors exactly what exploits to attempt or search for.

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @SamJUK. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. 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-Bravo]

Hi @SamJUK,

Thanks for your reporting and collaboration.

We have verified the issue in Latest 2.4-develop instance and the issue is reproducible.Kindly refer the screenshots.

We see a lovely page telling us exactly the Magento version.

Hence Confirming the issue.

Thanks.

[github-jira-sync-bot]

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

[m2-assistant]

✅ Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[Serfe-com]

For those who are exposed by an apache configuration on a server and don't want to fiddle with the code, a quick solution can be to modify setup/.htaccess by adding the lines:

   location ~ ^/setup/index.php {
+      Order Allow,Deny
+      Deny from all
   } 

This way access to setup will be forbidden by direct request when in production server.

[SamJUK]

@Serfe-com Thanks for that, should cover Apache servers well.

As far as I am aware, Nginx wont read .htaccess files. So will still need its config updated.
Or if you do not have access to the web server configs, you can instead drop the version line from the setup view file.

Nginx Configuration

 location ~* ^/setup($|/) {
     root $MAGE_ROOT;
     location ~ ^/setup/index.php {
+        deny all;
         fastcgi_pass   fastcgi_backend;

         fastcgi_param  PHP_FLAG  "session.auto_start=off \n suhosin.session.cryptua=off";

Application Level

--- setup/view/magento/setup/index.phtml
+++ setup/view/magento/setup/index.phtml
@@ -10,7 +10,6 @@
     <main class="page-content">
         <section data-section="landing" class="page-landing">
             <img class="logo" src="<?= $this->basePath() ?>/pub/images/magento-logo.svg" alt="Magento"/>
-            <p class="text-version">Version <?= htmlspecialchars($this->version, ENT_COMPAT) ?></p>
             <p class="text-welcome">
                 Welcome to Magento Admin, your online store headquarters.
                 <br>