wabac.js has XSS vulnerability in 404 error handling logic
webrecorder wabac.js
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @webrecorder/wabac npm |
|
|
| replaywebpage npm |
|
|
| @webrecorder/archivewebpage npm |
webrecorder wabac.js
| Product | Affected | Fixed in |
|---|---|---|
| @webrecorder/wabac npm |
|
|
| replaywebpage npm |
|
|
| @webrecorder/archivewebpage npm |
< 0.15.4
|
wabac.js provides a full web archive replay system, or 'wayback machine', using Service Workers. A Reflected Cross-Site Scripting (XSS) vulnerability exists in the 404 error handling logic of wabac.js v2.23.10 and below. The parameter `requestURL` (derived from the original request target) is directly embedded into an inline `<script>` block without sanitization or escaping. This allows an attacker to craft a malicious URL that executes arbitrary JavaScript in the victim’s browser. The scope may be limited by CORS policies, depending on the situation in which wabac.js is used. The vulnerability is fixed in wabac.js v2.23.11.
From the CVE record · GitHub_M
wabac.js embeds an unescaped request URL in an inline script when handling a 404 error. An attacker can craft a URL that executes JavaScript in a victim’s browser if the victim opens it; CORS policies may limit the impact depending on how wabac.js is used.
Teams using npm @webrecorder/wabac before 2.23.11, replaywebpage before 2.3.17, or @webrecorder/archivewebpage before 0.15.4 should check their installations.