Feedback on page: src/troubleshooting/known-issues-patches-attached/0-day-vulnerability-patch.md
ak77-prime opened this issue · 2 comments
ak77-prime commented
Article URL
https://support.magento.com/hc/en-us/articles/4426353041293
Description
Provide an additional section at the bottom of the article:
How to tell whether the MDVA-43395 and MDVA-43443 patches have been successfully applied using the "magento-patches" command (with the caveat we aren't able to provide the steps to verify that the vulnerability has been patched)
- Install the Quality Patches Tool
- Run this command:
``vendor/bin/magento-patches -n status |grep "43395|43443|Status" - You should see this output - MDVA-43395 returns a status of N/A and MDVA-43443 returns a status of Applied
║ Id │ Title │ Category │ Origin │ Status │ Details ║
║ N/A │ ../m2-hotfixes/MDVA-43443_EE_2.4.3-p1_COMPOSER_v1.patch │ Other │ Local │ Applied │ Patch type: Custom ║
║ MDVA-43395 │ Parser token fix │ Other │ Adobe Commerce Support │ N/A │ Patch type: Required ║
║ N/A │ ../m2-hotfixes/MDVA-43395_EE_2.4.3-p1_COMPOSER_v1.patch │ Other │ Local │ N/A │ Patch type: Custom ║
Content checklist
- The topic provides troubleshooting/best practice for verifying that the patch has been applied.
- Information in this topic is relevant for
- Magento Commerce version Already covered in the article.
- Magento Commerce Cloud version Already covered in the article.
- Magento Open Source version All.
- Extension or technology (Fastly, New Relic etc) version ____.
Additional information/resources
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
jmenn commented
Hi Anthony!
Thanks for the submission! I have created this ticket for it:
https://jira.corp.adobe.com/browse/MSKB-1477
almarchenko commented
@ak77-prime we are waiting for your approve in the internal repo