CVE-2020-15245: Email verification bypass in Sylius
Impact The user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one).
Patches Patch has been provided for Sylius 1.6.x and newer - 1.6.9, 1.7.9, 1.8.3. Versions older than 1.6 are not covered by our security support anymore.
Workarounds If for whatever reason you are not able to upgrade your application version, you may resolve this issue on your own by creating a custom event listener, which will listen to the sylius.customer.preupdate event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain /admin prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.
Acknowledgements
This security issue has been reported by Mircea Silviu (@decemvre), thanks a lot!
For more information
If you have any questions or comments about this advisory: Email us at security@sylius.com
Other sources
CVE-2020-15245: Ability to switch customer email address on account detail page and stay verified
In Sylius before versions 1.6.9, 1.7.9 and 1.8.3, the user may register in a shop by email mail@example.com, verify it, change it to the mail another@domain.com and stay verified and enabled. This may lead to having accounts addressed to totally different emails, that were verified. Note, that this way one is not able to take over any existing account (guest or normal one). The issue has been patched in Sylius 1.6.9, 1.7.9 and 1.8.3. As a workaround, you may resolve this issue on your own by creating a custom event listener, which will listen to the sylius.customer.preupdate event. You can determine that email has been changed if customer email and user username are different. They are synchronized later on. Pay attention, to email changing behavior for administrators. You may need to skip this logic for them. In order to achieve this, you should either check master request path info, if it does not contain /admin prefix or adjust event triggered during customer update in the shop. You can find more information on how to customize the event here.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is CVE-2020-15245?
CVE-2020-15245 is a vulnerability that allows the user to switch the customer's email address on the account detail page and stay verified.
What is the severity of CVE-2020-15245?
CVE-2020-15245 has a severity value of 4.3, which is classified as medium.
Which versions of Sylius are affected by CVE-2020-15245?
The versions of Sylius affected by CVE-2020-15245 are 1.0.0 up to 1.6.9, 1.7.0 up to 1.7.9, and 1.8.0 up to 1.8.3.
How can I fix CVE-2020-15245?
To fix CVE-2020-15245, it is recommended to update Sylius to version 1.6.9, 1.7.9, or 1.8.3, depending on the affected version.
Is there any additional information about CVE-2020-15245?
Yes, you can find more information about CVE-2020-15245 in the references: [GitHub Advisory](https://github.com/Sylius/Sylius/security/advisories/GHSA-6gw4-x63h-5499) and [GitHub Commit](https://github.com/Sylius/Sylius/commit/60636d711a4011e8694d10d201b53632c7e8ecaf).