Skip to content

Security Vulnerability Assessment Report

🚨 Security Vulnerability Assessment Report

Section titled “🚨 Security Vulnerability Assessment Report”

Critical Finding: DOM Clobbering XSS Vulnerability in Rollup

Section titled “Critical Finding: DOM Clobbering XSS Vulnerability in Rollup”
  • CVE: DOM Clobbering Gadget in rollup bundled scripts
  • Severity: High (8.3/10)
  • Affected Package: rollup version 0.41.6
  • Location: services/ai-gateway/node_modules/uri-js/package.json (devDependencies)
  • Fix Version: Rollup 2.79.2+

The vulnerable rollup version is in the devDependencies of uri-js, which means:

  • Not bundled in production - Dev dependencies are not included in production builds
  • Build-time only - Only affects the uri-js library’s own build process
  • No runtime exposure - The vulnerability cannot be exploited in the running application
services/ai-gateway/node_modules/uri-js/package.json
"devDependencies": {
"rollup": "^0.41.6", // ← Vulnerable version
// ... other dev deps
}

The vulnerability affects:

  • Scripts that use import.meta.url
  • Output formats: cjs, umd, iife
  • DOM Clobbering via document.currentScript
  • Rollup version: 4.50.1 (via Vite) - SAFE
  • npm audit: 0 vulnerabilities found
  • Production dependencies: All secure
  • AI Gateway: uri-js 4.4.1 - SAFE (vulnerable rollup is dev-only)
  • All services: 0 vulnerabilities in production dependencies
  • All projects: Using modern, secure rollup versions
  1. Dev dependency isolation: Vulnerable rollup not in production
  2. Modern rollup versions: Main app uses secure 4.50.1
  3. No runtime exposure: Vulnerability cannot be exploited
  4. Build process separation: Each service builds independently
  1. Monitor uri-js updates - Watch for newer versions that update rollup
  2. Security scanning - Add automated security scanning to CI/CD
  3. Dependency auditing - Regular npm audit in all projects
  1. Override vulnerable deps: Use npm overrides to force secure versions
  2. Alternative libraries: Consider replacing uri-js if updates are slow
  3. Build isolation: Ensure dev dependencies never leak to production
Terminal window
# Main application
npm audit --audit-level=high
# Result: 0 vulnerabilities ✅
# AI Gateway service
cd services/ai-gateway && npm audit --audit-level=high
# Result: 0 vulnerabilities ✅
# All production dependencies secure ✅

🟢 RISK LEVEL: LOW

The reported vulnerability exists but poses minimal risk because:

  1. It’s in a dev dependency, not production code
  2. It doesn’t affect the running application
  3. All production dependencies are secure
  4. Modern rollup versions are used in main builds

The application is SECURE for production deployment.

  • Assess vulnerability impact
  • Confirm dev dependency isolation
  • Verify production security
  • Monitor for uri-js updates (ongoing)
  • Add security scanning to CI/CD (optional)

Report generated: September 17, 2025 Assessment: The vulnerability is present but does not affect production security