GHSA-cjw8-79x6-5cj4 jsPDF has Shared State Race Condition in addJS Plugin

• npm jspdf: < 4.1.0 → fixed in 4.1.0

Impact The addJS method in the jspdf Node.js build utilizes a shared module-scoped variable (text) to store JavaScript content. When used in a concurrent environment (e.g., a Node.js web server), this variable is shared across all requests. If multiple requests generate PDFs simultaneously, the JavaScript content intended for one user may be overwritten by a subsequent request before the document is generated. This results in Cross-User Data Leakage, where the PDF generated for User A contains the JavaScript payload (and any embedded sensitive data) intended for User B. Typically, this only affects server-side environments, although the same race conditions might occur if jsPDF runs client-side. ```js import { jsPDF } from "jspdf"; const docA = new jsPDF(); const docB = new jsPDF(); // 1. User A sets their script (stored in shared 'text' variable) docA.addJS('console.log("Secret A");'); // 2. User B sets their script (overwrites shared 'text' variable) docB.addJS('console.log("Secret B");'); // 3. User A saves their PDF (reads current 'text' variable) docA.save("userA.pdf"); // Result: userA.pdf contains "Secret B" instead of "Secret A" ``` Patches The vulnerability has been fixed in [email protected]. The fix moves the shared variable into the function scope, ensuring isolation between instances. Workarounds Avoid using the addJS method in concurrent server-side environments. If usage is required, ensure requests are processed sequentially (e.g., using a queue) rather than in parallel.