CVE-2020-15245 Email verification bypass in Sylius

Medium 4.3 Published Updated

Attackers can bypass email verification by changing their email after initial verification, resulting in unverified accounts being marked as verified.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2020-15245?

CVE-2020-15245 is a medium-severity vulnerability in Sylius, published on 19 Oct 2020. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.pre_update 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.

Weakness: CWE-862, CWE-79

Which versions are affected by CVE-2020-15245?

6 open source packages ship an affected version, including sylius/sylius. It affects 1 product.

PackageAffectedFixed in
sylius/sylius PackagistFrom 1.0.01.6.9
sylius/sylius PackagistFrom 1.0.01.6.9
sylius/sylius PackagistFrom 1.7.01.7.9
sylius/sylius PackagistFrom 1.7.01.7.9
sylius/sylius PackagistFrom 1.8.01.8.3
sylius/sylius PackagistFrom 1.8.01.8.3

Products include Sylius Sylius.

How do I fix CVE-2020-15245?

Upgrade sylius/sylius to a fixed version for your release line: 1.6.9, 1.7.9 or 1.8.3.

Is CVE-2020-15245 being exploited?

There is no known exploitation of CVE-2020-15245 in the wild and no public exploit code.

Sources

Also known as GHSA-6gw4-x63h-5499.

Is CVE-2020-15245 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free