Closed Dargon789 closed 2 weeks ago
β Deploy failed!
[!CAUTION] Test run failed
St.:grey_question: |
Category | Percentage | Covered / Total |
---|---|---|---|
π‘ | Statements | 73.5% (-0.03% π») |
13493/18359 |
π΄ | Branches | 51.34% (-0.01% π») |
3282/6393 |
π΄ | Functions | 56.99% | 1960/3439 |
π‘ | Lines | 75.19% (-0.04% π») |
12269/16318 |
Report generated by π§ͺjest coverage report action from 970ccd08be4a50a99d0937e5c2c6af9998b5212e
Fixes https://github.com/Dargon789/safe-wallet-web/security/code-scanning/3
To fix the SSRF vulnerability, we should avoid using user input directly in the hostname of the URL. Instead, we can use an allow-list of known safe URLs or domains. This ensures that only pre-approved URLs can be used in the request, mitigating the risk of SSRF.
appUrl
against this allow-list before making the request.appUrl
is not in the allow-list, throw an error or handle it appropriately.Suggested fixes powered by Copilot Autofix. Review carefully before merging.