chore: SSO/SAML hardening

[paustint]

No description provided.

[Copilot]

Pull request overview

This PR hardens the SSO/SAML authentication surface area by pinning a patched XML DOM dependency, tightening SAML assertion replay/age controls, and adding additional crypto input validation with corresponding tests.

Changes:

• Force @xmldom/xmldom to ^0.8.13 via pnpm overrides to pick up security patches on the SAML validation dependency chain.
• Add explicit malformed/truncated payload guarding in decryptSecret (AES-256-GCM) and test coverage for the clearer error.
• Strengthen SAML response handling by bounding assertion age, extending consumed-assertion TTL, and enforcing mandatory assertion replay protection keyed from the verified assertion; add unit tests for first-use/replay/fail-closed behavior.

Reviewed changes

Copilot reviewed 5 out of 6 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
pnpm-workspace.yaml	Adds an override to force a patched @xmldom/xmldom for SAML-related transitive deps.
pnpm-lock.yaml	Updates lockfile overrides and resolved @xmldom/xmldom version to 0.8.13 across dependents.
libs/auth/server/src/lib/sso-crypto.util.ts	Adds documentation on IV length choice and guards against undersized encrypted payloads before slicing.
libs/auth/server/src/lib/saml.service.ts	Introduces max assertion age and mandatory replay detection derived from the verified assertion; adjusts consumed-assertion TTL.
libs/auth/server/src/lib/tests/sso-crypto.util.spec.ts	Adds a test asserting the new clear “too short” error for undersized ciphertext payloads.
libs/auth/server/src/lib/tests/saml.service.spec.ts	Adds tests for first-use acceptance, replay rejection, and fail-closed behavior when no assertion identifier can be derived.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vitest@​4.0.9
	@​types/​gapi.client.drive-v3@​0.0.5
	nx@​22.7.2
	husky@​9.1.7
	document.contains@​1.0.2
	eslint-config-next@​16.2.6
	@​vitest/​coverage-v8@​4.0.9
	electron-builder@​26.13.1
	@​types/​express-http-proxy@​1.6.7
	@​jetstreamapp/​simple-xml@​1.1.1
	@​types/​react-router-dom@​5.3.3
	@​types/​unzipper@​0.10.11
	@​tsconfig/​node22@​22.0.5
	jszip@​3.10.1
	webextension-polyfill@​0.12.0
	web-ext@​8.10.0
	@​types/​express@​5.0.6
	@​nx/​esbuild@​22.7.2
	@​babel/​preset-react@​7.29.7
	@​typescript-eslint/​parser@​8.46.2
	@​types/​js-yaml@​4.0.9
	@​types/​archiver@​6.0.4
	@​nx/​playwright@​22.7.2
	@​swc/​helpers@​0.5.18
	@​commitlint/​cli@​20.5.3
	@​babel/​preset-typescript@​7.29.7
	@​types/​gapi.auth2@​0.0.61
	@​oslojs/​otp@​1.1.0
	@​types/​multer@​2.1.0
	@​types/​pg@​8.20.0
	esbuild@​0.27.7
	@​types/​express-session@​1.19.0
	dexie-react-hooks@​1.1.7
See 197 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: When Vitest UI server is listening, arbitrary file can be read and executed CVE: GHSA-5xrq-8626-4rwp When Vitest UI server is listening, arbitrary file can be read and executed (CRITICAL) Affected versions: < 4.1.0 Patched version: 4.1.0 From: package.json → npm/vitest@4.0.9 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vitest@4.0.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm @react-email/ui is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: package.json → npm/@react-email/ui@6.4.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@react-email/ui@6.4.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[Copilot]

Pull request overview

Copilot reviewed 5 out of 6 changed files in this pull request and generated no new comments.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported