Impact
Any users who are using the wget or dom extractors and view the content they output.
The impact is potentially severe if you are logged in to the ArchiveBox admin site in the same browser session and view an archived malicious page designed to target your ArchiveBox instance. Malicious JS could potentially act using your logged-in admin credentials and add/remove/modify snapshots, add/remove/modify ArchiveBox users, and generally do anything an admin user could do.
The impact is less severe for non-logged-in users, as malicious JS cannot modify any archives, but it can still read all the other archived content by fetching the snapshot index and iterating through it.
Because all of ArchiveBox's archived content is served from the same host and port as the admin panel, when archived pages are viewed the JS executes in the same context as all the other archived pages (and the admin panel), defeating most of the browser's usual CORS/CSRF security protections and leading to this issue.
Patches
Follow here for progress on mitigating this issue: #239
Workarounds
Disable the risky extractors by setting archivebox config --set SAVE_WGET=False SAVE_DOM=False, ensure you are always logged out, or serve only a static HTML version of your archive.
References
Impact
Any users who are using the
wgetordomextractors and view the content they output.The impact is potentially severe if you are logged in to the ArchiveBox admin site in the same browser session and view an archived malicious page designed to target your ArchiveBox instance. Malicious JS could potentially act using your logged-in admin credentials and add/remove/modify snapshots, add/remove/modify ArchiveBox users, and generally do anything an admin user could do.
The impact is less severe for non-logged-in users, as malicious JS cannot modify any archives, but it can still read all the other archived content by fetching the snapshot index and iterating through it.
Because all of ArchiveBox's archived content is served from the same host and port as the admin panel, when archived pages are viewed the JS executes in the same context as all the other archived pages (and the admin panel), defeating most of the browser's usual CORS/CSRF security protections and leading to this issue.
Patches
Follow here for progress on mitigating this issue: #239
Workarounds
Disable the risky extractors by setting
archivebox config --set SAVE_WGET=False SAVE_DOM=False, ensure you are always logged out, or serve only a static HTML version of your archive.References