vuln-28982-2-4-5x-v2-composer.patch not apply in Magento version 2.4.5

[sw-tt-divyangasodiya1]

Preconditions and environment

Adobe Commerce

• Magento version : 2.4.5

Steps to reproduce

We already 2 composer patch in m2-hotfixes folder as below

AC-12485_Hotfix.composer.patch
VULN-27015-2.4.5x_v2.composer.patch

Then we added file vuln-28982-2-4-5x-v2-composer.patch

when we commit and push it in shows failure.

Expected result

The patch should be applied.

Actual result

Git commit shows failure

Applying hot-fixes
Patch ../m2-hotfixes/AC-12485_Hotfix.composer.patch was already applied
Patch ../m2-hotfixes/VULN-27015-2.4.5x_v2.composer.patch was already applied
Error: patch /app/m2-hotfixes/vuln-28982-2-4-5x-v2-composer.patch can't be applied
Start of rollback
Patch ../M2-HOTFIXES/VULN-27015-2.4.5X_V2.COMPOSER.PATCH has been reverted
Patch ../M2-HOTFIXES/AC-12485_HOTFIX.COMPOSER.PATCH wasn't applied
End of rollback
Magento 2 B2B Edition, version 2.4.5.0
Applying patch /app/m2-hotfixes/vuln-28982-2-4-5x-v2-composer.patch failed.
error: patch failed: vendor/magento/module-customer/Model/AccountManagement.php:879
error: vendor/magento/module-customer/Model/AccountManagement.php: patch does not apply
error: patch failed: vendor/magento/module-customer/Model/AccountManagementApi.php:6
error: vendor/magento/module-customer/Model/AccountManagementApi.php: patch does not apply
error: vendor/magento/module-customer/Plugin/AsyncRequestCustomerGroupAuthorization.php: already exists in working directory
error: vendor/magento/module-customer/Test/Unit/Model/AccountManagementApiTest.php: already exists in working directory
error: patch failed: vendor/magento/module-customer/Test/Unit/Model/AccountManagementTest.php:1222
error: vendor/magento/module-customer/Test/Unit/Model/AccountManagementTest.php: patch does not apply
error: vendor/magento/module-customer/Test/Unit/Plugin/AsyncRequestCustomerGroupAuthorizationTest.php: already exists in working directory
error: patch failed: vendor/magento/module-customer/composer.json:35
error: vendor/magento/module-customer/composer.json: patch does not apply

and so on...

Additional information

No response

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 @sw-tt-divyangasodiya1. 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.

[m2-assistant]

Hi @engcom-Hotel. 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-Hotel]

Hello @sw-tt-divyangasodiya1,

We are in discussion for this issue with the internal team. Meanwhile we are moving this issue on hold.

Thanks

[sw-tt-divyangasodiya1]

Hello,

This issue resolved by upgrading ece-tools in the production branch, and the fix is already included in the Commerce patches.

Thanks