Bump dompurify and swagger-ui-react in /frontend

[dependabot]

Bumps dompurify to 3.1.6 and updates ancestor dependency swagger-ui-react. These dependencies need to be updated together.

Updates dompurify from 3.0.4 to 3.1.6

Release notes

Sourced from dompurify's releases.

DOMPurify 3.1.6

• Fixed an issue with the execution logic of attribute hooks to prevent bypasses, thanks @​kevin-mizu
• Fixed an issue with element removal leading to uncaught errors through DOM Clobbering, thanks @​realansgar
• Fixed a minor problem with the bower file pointing to the wrong dist path
• Fixed several minor typos in docs, comments and comment blocks, thanks @​Rotzbua
• Updated several development dependencies

DOMPurify 3.1.5

• Fixed a minor issue with the dist paths in bower.js, thanks @​HakumenNC
• Fixed a minor issue with sanitizing HTML coming from copy&paste Word content, thanks @​kakao-bishop-cho

DOMPurify 3.1.4

• Fixed an issue with the recently implemented isNaN checks, thanks @​tulach
• Added several new popover attributes to allow-list, thanks @​Gigabyte5671
• Fixed the tests and adjusted the test runner to cover all branches

DOMPurify 3.1.3

• Fixed several mXSS variations found by and thanks to @​kevin-mizu & @​Ry0taK
• Added better configurability for comment scrubbing default behavior
• Added better hardening against Prototype Pollution attacks, thanks @​kevin-mizu
• Added better handling and readability of the nodeType property, thanks @​ssi02014
• Fixed some smaller issues in README and other documentation

DOMPurify 3.1.2

• Addressed and fixed a mXSS variation found by @​kevin-mizu
• Addressed and fixed a mXSS variation found by Adam Kues of Assetnote
• Updated tests for older Safari and Chrome versions

DOMPurify 3.1.1

• Fixed an mXSS sanitiser bypass reported by @​icesfont
• Added new code to track element nesting depth
• Added new code to enforce a maximum nesting depth of 255
• Added coverage tests and necessary clobbering protections

Note that this is a security release and should be upgraded to immediately. Please also note that further releases may follow as the underlying vulnerability is apparently new and further variations may be discovered.

DOMPurify 3.1.0

• Added new setting SAFE_FOR_XML to enable better control over comment scrubbing
• Updated README to warn about happy-dom not being safe for use with DOMPurify yet
• Updated the LICENSE file to show the accurate year number
• Updated several build and test dependencies

DOMPurify 3.0.11

• Fixed another conditional bypass caused by Processing Instructions, thanks @​Ry0taK
• Fixed the regex for HTML Custom Element detection, thanks @​AlekseySolovey3T

DOMPurify 3.0.10

• Fixed two possible bypasses when sanitizing an XML document and later using it in HTML, thanks @​Slonser
• Bumped up some build and test dependencies

... (truncated)

Commits

• 4083a90 Merge pull request #978 from cure53/main
• 90a10a1 fix: Fixed a typo on the README
• 65df042 chore: Preparing 3.1.6 release
• 6e03334 fix: Made sure that remove() is not called directly from node
• 00fc06c fix: Fixed a DOM clobbering issue leading to an error being thrown
• f8c2ef5 Merge pull request #977 from cure53/dependabot/npm_and_yarn/multi-99ca4f73d8
• e5112ec build(deps): bump ws and socket.io-adapter
• 9978cec docs: Added better security warning about SAFE_FOR_XML to README
• fa542df fix: Changed the order for attribute checks slightly for safer hooks
• b8b552c Merge pull request #975 from cure53/dependabot/npm_and_yarn/multi-2d3aef8690
• Additional commits viewable in compare view

Updates swagger-ui-react from 5.1.1 to 5.18.2

Release notes

Sourced from swagger-ui-react's releases.

Swagger UI v5.18.2 Released!

5.18.2 (2024-11-07)

Bug Fixes

• update Scarf.js to v1.4.0 to avoid breaking Vitest (#10204) (adc1c3c), closes #10197

Swagger UI v5.18.1 Released!

5.18.1 (2024-11-05)

Bug Fixes

• docker: return explicit Node.js installation (#10198) (3e3dfc6), closes #10195

Swagger UI v5.18.0 Released!

5.18.0 (2024-11-05)

Features

• analytics: use Scarf.js to provide anonymized installation analytics (#10194) (fb55b9c)

---

Anonymized analytics

SwaggerUI uses Scarf to collect anonymized installation analytics. These analytics help support the maintainers of this library and ONLY run during installation. To opt out, you can set the scarfSettings.enabled field to false in your project's package.json:

// package.json
{
  // ...
  "scarfSettings": {
    "enabled": false
  }
  // ...
}

Alternatively, you can set the environment variable SCARF_ANALYTICS to false as part of the environment that installs your npm packages, e.g., SCARF_ANALYTICS=false npm install.

Swagger UI v5.17.14 Released!

5.17.14 (2024-05-28)

Bug Fixes

• system: remediate component wrapping functionality (#9978) (8aa5292), closes #9919

... (truncated)

Commits

• 3c7e281 chore(release): cut the v5.18.2 release
• 1dd1f7c chore(dist): update Scarf.js to v1.4.0 (#10205)
• adc1c3c fix: update Scarf.js to v1.4.0 to avoid breaking Vitest (#10204)
• 7b84da5 chore(deps-dev): bump release-it from 17.5.0 to 17.10.0 (#10202)
• e5d00e8 chore(deps-dev): bump json-merger from 1.1.10 to 2.0.0 (#10201)
• 8fdf0d3 chore(deps-dev): bump jsdom from 24.0.0 to 25.0.1 (#10200)
• 05b7aff chore(docker): disable apk cache (#10203)
• 91b6e13 chore(deps-dev): bump husky from 9.0.11 to 9.1.6 (#10199)
• e5addb1 chore(release): cut the v5.18.1 release
• 3e3dfc6 fix(docker): return explicit Node.js installation (#10198)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.