Information and link in README.md file related to Security issue reporting should be updated

[sdzhepa]

Preconditions (*)

1. the Readme on https://github.com/magento/magento2 still says to create Bugcrowd reports for security vulns. Since the program is taken down the link 404's
2. Now in use HackerOne for these purposes

Steps to reproduce (*)

1. Go to https://github.com/magento/magento2/blob/2.3-develop/README.md
2. Scroll to "Reporting Security Issues" section

Expected result (*)

1. Text and link should be updated and use "HackerOne" instead of "Bugcrowd "
   Example of Expected code/text
   ## Reporting Security Issues
To report security vulnerabilities in Magento software or web sites, please create a HackerOne account [there](https://hackerone.com/magento) to submit and follow-up your issue. Learn more about reporting security issues [here](https://magento.com/security/reporting-magento-security-issue).

Actual result (*)

1. Current text and link related to 'Bugcrowd researcher account there ' leads to 404 page
   Example of Actual code/text
   ## Reporting Security Issues
To report security vulnerabilities in Magento software or web sites, please create a Bugcrowd researcher account [there](https://bugcrowd.com/magento) to submit and follow-up your issue. Learn more about reporting security issues [here](https://magento.com/security/reporting-magento-security-issue).

[m2-assistant]

Hi @sdzhepa. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@sdzhepa do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[magento-engcom-team]

@sdzhepa Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess
• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@sdzhepa Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess
• Add "Reproduced on " label(s) to this ticket based on verification result

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

@sdzhepa Thank you for verifying the issue.

Unfortunately, not enough information was provided to acknowledge ticket. Please consider adding the following:

• Add "Component: " label(s) to this ticket based on verification result. If uncertain, you may follow the best guess

Once all required information is added, please add label "Issue: Confirmed" again.
Thanks!

[magento-engcom-team]

✅ Confirmed by @sdzhepa
Thank you for verifying the issue. Based on the provided information internal tickets MAGETWO-99059 were created

Issue Available: @sdzhepa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[magento-engcom-team]

Hi @sdzhepa. Thank you for your report.
The issue has been fixed in #22195 by @mautz-et-tong in 2.3-develop branch
Related commit(s):

• 34bd8bd793de2aad34c461aad62a1a3984fb509a

The fix will be available with the upcoming 2.3.2 release.