Q CSP: backport replace crypto polyfill with an empty module
Description
Summary: Backport to the b5.1 branch, making it available in a Quesnelia-compatible release.
CSP Request Details
1. Describe issue impact on business:
This change removes a third-party dependency containing a critical security vulnerability from the build toolchain: https://security.snyk.io/vuln/SNYK-JS-ELLIPTIC-8187303
2. What institutions are affected? (field “Affected Institutions” in Jira to be populated)
All
3. What is the workaround if exists?
None
4. What areas will be impacted by fix (i.e. what areas need to be retested)
UI bundle generation
5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high)
Replace the vulnerable package with a do-nothing shim, causing code that relies on it to fallback on a safe alternative. LoE is less than one day (it's a one-line change). Risk is low.
6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.
To test, build a UI bundle. If it works, you're good. LoE is less than one day (installing and building platform-complete probably takes ~10 minutes).
7. What is the roll back plan in case the fix does not work?
Continue to use the previous release. This vulnerability is in the build toolchain, not the final build itself.
Summary: Backport to the
b5.1
branch, making it available in a Quesnelia-compatible release.