Lack of email length validation exposes the website id during customer creation

[ivanaugustobd]

Preconditions and environment

• A clean install of any Magento version from 2.4.6 to 2.4.9

Steps to reproduce

1. Navigate to /customer/account/create
2. Try to create a customer with an e-mail containing 256 characters or more, eg.:

abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.0123456789@abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxy.com

Expected result

An "Email" uses too many characters. or similar exception should be thrown.

Actual result

A raw exception is being thrown instead, exposing the website id in the process:

No such entity with email = abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.0123456789@abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxyz.abcdefghijklmnopqrstuvwxy.com, websiteId = 1

Found by: Dilnoza (QA team)

Additional information

The customer_entity.email field at database has a 255 char limit, causing the $customerModel->save(); operation at the customer repository to fail silently. The reported raw exception is thrown within the customer repository save() method at app/code/Magento/Customer/Model/ResourceModel/CustomerRepository.php:L320.

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 @ivanaugustobd. 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.

[github-jira-sync-bot]

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

[ivanaugustobd]

Workaround: add such validation directly at the database, in the customer email attribute customer_eav_attribute.validation_rules:

UPDATE customer_eav_attribute cea
JOIN eav_attribute ea ON ea.attribute_id = cea.attribute_id
JOIN eav_entity_type eet ON eet.entity_type_id = ea.entity_type_id
SET cea.validate_rules = '{"input_validation":"email","max_text_length":255}'
WHERE eet.entity_type_code = 'customer' AND ea.attribute_code = 'email';

This will ensure a user friendly message without the website technical info:

[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 @ivanaugustobd,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and we are able to reproduce the issue.Please refer the screenshot.

A raw exception is being thrown instead, exposing the website id in the process.Hence Confirming the issue.

Thanks.