Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The latest run of the OWASP Dependency Check tool, on which this ticket is based, shows some things that need to be addressed.
Major changes
create-react-app
/`react-scripts to Vite.request
dependency from Alloy.src/utils/parseUrl.js
off of the vulnerableparse-uri
Remaining vulnerabilities
async:2.6.4
&async:3.2.3
vitest
(our unit testing framework) and v2.6.4 is a dependency of thetestcafe-browser-provider-saucelabs
(what connects our functional test framework to our browser automation hosting). It is a Regex Denial of Service vulnerability. Since they are in our testing frameworks, the worst that could happen is that our tests hang.esbuild:0.24.2
vite
(the build tool the sandbox now uses) and ofvitest
(which usesvitest
internally). According to thevite
team, this vulnerability inesbuild
does not affectvite
.graphql:16.10.0
graphql
is a dependency of the@vitest/coverage
dependency for our unit tests. This is not a vulnerable part of the applicationRelated Issue
PDCL-12965: AEP WebSDK - Outdated Vulnerable Software - Critical (9.8)
Closes #1231
Motivation and Context
Screenshots (if appropriate):
Types of changes
Checklist: