Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strict content security policy (CSP) enforcement compatibility #98

Open
lytesaber opened this issue Jul 23, 2024 · 0 comments
Open

Strict content security policy (CSP) enforcement compatibility #98

lytesaber opened this issue Jul 23, 2024 · 0 comments

Comments

@lytesaber
Copy link

Affected Versions

  • zip/magento2 - 1.2.5 or previous release
  • Magento 2.4.7 and up
  • Magento 2.4.6-p6
  • Magento 2.4.5-p8
  • Magento 2.4.4-p9

Issue
As of the most recent security patch releases and the Magento 2.4.7 release Adobe has enforced strict content security policy (CSP) instead of the report-only configuration from previous releases. In my case upgrading from 2.4.5-p7 to 2.4.5-p8 enforced this change, in testing I've found CSP-related errors thrown in console when proceeding to the checkout.

This is outlined by Adobe in the patch release notes that strict CSP is now enforced:
https://experienceleague.adobe.com/en/docs/commerce-operations/release/notes/security-patches/2-4-5-patches#additional-security-enhancements

Workaround
There is a workaround outlined by Sansec by turning CSP back to report-only mode however this will be non-compliant with the changes coming into effect with PCI DSS as of April next year.
https://sansec.io/guides/magento-csp#disable-strict-csp-on-checkout

Solution
Zip must be patched to be compatible with Magento when strict content security policy (CSP) is enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant