The Content-Security-Policy directive 'frame-ancestors' does not support the source expression ''unsafe-inline''

[minhluan259]

Preconditions (*)

1. Magento 2.4.2-p1 with sample data
2. Chrome v91

Steps to reproduce (*)

1. Open console in Google Chrome (F12)
2. Reload the homepage

Expected result (*)

1. Console without error

Actual result (*)

1. Console is displaying error:
   The Content-Security-Policy directive 'frame-ancestors' does not support the source expression ''unsafe-inline''

How to solve 'frame-ancestors' issue?

[m2-assistant]

Hi @minhluan259. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• 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, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[mrtuvn]

Seem you have add whitelist csp to your external resources. Otherwises browser will raise error like that
Ex: https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Csp/etc/csp_whitelist.xml

[TheRealHunzik]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @TheRealHunzik. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @TheRealHunzik, here is your Magento Instance: https://417250d6ae3dad506caa89980d793a88-2-4-develop.instances.magento-community.engineering
Admin access: https://417250d6ae3dad506caa89980d793a88-2-4-develop.instances.magento-community.engineering/admin_c253
Login: b17d726b
Password: 7814a27bf253

[minhluan259]

@mrtuvn it's not about whitelist issue, because on default luma theme we do not have any iframe (object, embed, ... https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors ) tags.
the problem is 'unsafe-inline' only support by 'script-src'
and 'frame-ancestors' does not support the source expression ''unsafe-inline''
https://content-security-policy.com/unsafe-inline/

[m2-assistant]

Hi @engcom-Echo. 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).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - 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-Echo]

Hi Minhluan259,

Please refer the devdocs link - https://devdocs.magento.com/guides/v2.4/extension-dev-guide/security/content-security-policies.html
For CSP related information.

Hope this link will help you resolve this issue that you are getting.

Let me know , if the information does not suffice your query.

Thanks

[minhluan259]

@engcom-Echo please read this:

@mrtuvn it's not about whitelist issue, because on default luma theme we do not have any iframe (object, embed, ... https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/frame-ancestors ) tags.
the problem is 'unsafe-inline' only support by 'script-src'
and 'frame-ancestors' does not support the source expression ''unsafe-inline''
https://content-security-policy.com/unsafe-inline/

[refueledinc]

I'm in agreement with @minhluan259 - the issue is happening because frame-ancestors does not support unsafe-inline.

The issue is reported as an error in console starting in Chrome v91.

[refueledinc]

I have not fully tested this, but changing line https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Csp/etc/config.xml#L109 to <inline>0</inline> appears to resolve the issue for me. Be sure to run php bin/magento c:c after the change.

[jmonrove]

Having the same issue on 2.4.2, Chrome 91.0.4472.77. @refueledinc's solution worked, but instead of doing it on the core file I added a section to my custom CSP extension

[jmonrove]

This is how mine looks: <?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Store:etc/config.xsd"> <default> <csp> <mode> <storefront> <report_uri>https://yoururl.com/</report_uri> </storefront> <admin> <report_uri>https://yoururl.com/</report_uri> </admin> </mode> <policies> <storefront> <frame-ancestors> <policy_id>frame-ancestors</policy_id> <self>1</self> <inline>0</inline> <eval>0</eval> <dynamic>0</dynamic> </frame-ancestors> </storefront> </policies> </csp> </default> </config>

…

On Thu, Jun 3, 2021 at 9:53 AM kunzi ***@***.***> wrote: Having the same issue on 2.4.2, Chrome 91.0.4472.77. @refueledinc <https://github.com/refueledinc>'s solution worked, but instead of doing it on the core file I added a section to my custom CSP extension Could you share your file as I could not get this fix to work in my custom module's config.xml? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHZMN4SV3BQCW2KE3NDDFXTTQ6XRLANCNFSM45ZSOOGQ> .

[pathakkrunal]

This is how mine looks: <report_uri>https://yoururl.com/</report_uri> <report_uri>https://yoururl.com/</report_uri> <policy_id>frame-ancestors</policy_id> 1 0 0 0
…
On Thu, Jun 3, 2021 at 9:53 AM kunzi @.***> wrote: Having the same issue on 2.4.2, Chrome 91.0.4472.77. @refueledinc https://github.com/refueledinc's solution worked, but instead of doing it on the core file I added a section to my custom CSP extension Could you share your file as I could not get this fix to work in my custom module's config.xml? — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#33101 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHZMN4SV3BQCW2KE3NDDFXTTQ6XRLANCNFSM45ZSOOGQ .

this help for me too
Thank you.

[davirs]

@jmonrove @pathakkrunal what is the solution? I think the repository not exists anymore..
Can you share the solution, please

[uisuru]

@refueledinc and @jmonrove solution is working.
@davirs

1. Create a new module or use an existing one.
2. Create a file called config.xml in the etc folder
3. put the following content to the file

<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Store:etc/config.xsd">
    <default>
        <csp>
            <policies>
                <storefront>
                    <frame-ancestors>
                        <inline>0</inline>
                    </frame-ancestors>
                </storefront>
            </policies>
        </csp>
    </default>
</config>

4. Delete static folder and clean cache

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@m2-community-project[bot] Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @engcom-Hotel
Thank you for verifying the issue. Based on the provided information internal tickets MC-42876 were created

Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[andrei-vdc]

@magento-engcom-team how come you agree that disabling security enhancements "fixes the issues" instead of guiding the community on how to create implementation that make use of your own SECURITY POLICIES?

[speedupmate]

2.4.3 affected logged in every page to console

The Content-Security-Policy directive 'frame-ancestors' does not support the source expression ''unsafe-inline''

[przmak]

So why this is closed while this error occurs ? :) I just checked a random site with magento 2.4.2 demo and it seems the error appears there
https://demo-m2.bird.eu/

[markshust]

Per the last comment, a fix was merged in with PR #33202 into the 2.4-develop branch. This means that it was fixed upstream (in a release branch) so it is resolved in all future versions of M2. To pull this into an older version like 2.4.2, you can create a diff patch to apply it to your store.

…

On Thu, Sep 23, 2021 at 6:43 AM Chris ***@***.***> wrote: So why this is closed while this error occurs ? :) I just checked a random site with magento 2.4.2 demo and it seems the error appears there https://demo-m2.bird.eu/ — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#33101 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADKWJL5SSJZ2QCKN4TIIQDUDMAG7ANCNFSM45ZSOOGQ> .

[YetiCGN]

I have not fully tested this, but changing line https://github.com/magento/magento2/blob/2.4-develop/app/code/Magento/Csp/etc/config.xml#L109 to <inline>0</inline> appears to resolve the issue for me. Be sure to run php bin/magento c:c after the change.

What also helps is deactivating the Csp module altogether: bin/magento module:disable Magento_Csp.

[ChameleonDevil]

What also helps is deactivating the Csp module altogether: bin/magento module:disable Magento_Csp.

I see alot of downvotes, basically because: What you actually inadvertently do when you disable the module, is to completely disable a new security feature created by Magento core, from the official documentation a better explanation than I can:

Content Security Policies (CSP) are a powerful tool to mitigate against Cross Site Scripting (XSS) and related attacks, including card skimmers, session hijacking, clickjacking, and more. Web servers send CSPs in response HTTP headers (namely Content-Security-Policy and Content-Security-Policy-Report-Only) to browsers that whitelist the origins of scripts, styles, and other resources

https://devdocs.magento.com/guides/v2.4/extension-dev-guide/security/content-security-policies.html

Perhaps you should try to look at re-enabling Magento_Csp and then use the csp_whitelist.xml to whitelist your trusted content in the future rather.

[gvasilakiss]

@magento give me 2.4-develop instance

[magento-deployment-service]

Hi @gvasilakiss. Thank you for your request. I'm working on Magento instance for you.

[magento-deployment-service]

Hi @gvasilakiss, here is your Magento Instance: https://417250d6ae3dad506caa89980d793a88-2-4-develop.instances.magento-community.engineering
Admin access: https://417250d6ae3dad506caa89980d793a88-2-4-develop.instances.magento-community.engineering/admin_4fc8
Login: d18f126d
Password: 37391f7d09fe