ArchiveBox is an open source self-hosted web archiving system. Any users who are using the `wget` extractor and view the content it outputs. 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 Javascript 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 Javascript 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. Version 0.9.0 contains a patch. As a mitigation for this issue would be to disable the wget extractor by setting `archivebox config --set SAVE_WGET=False`, ensure you are always logged out, or serve only a [static HTML version](https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#2-export-and-host-it-as-static-html) of your archive.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - ArchiveBox is an open source self-hosted web archiving system. Any users who are using the `wget`
    extractor and view the content it outputs. 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 Javascript 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 Javascript 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. Version 0.9.0 contains a patch. As a mitigation for this issue
    would be to disable the wget extractor by setting `archivebox config --set SAVE_WGET=False`, ensure you
    are always logged out, or serve only a [static HTML
    version](https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#2-export-and-host-it-as-
    static-html) of your archive. (CVE-2023-45815)

ID	Name	Product	Family	Severity
444479	SCA: security update for archivebox (GHSA-cr45-98w9-gwqx)	Tenable Cloud Security	SCA Checks	high
444479	SCA: security update for archivebox (GHSA-cr45-98w9-gwqx)	Tenable Self-Hosted Container Security	SCA Checks	high

Detections

Analytics

CVE-2023-45815

high

Tenable Plugins

high

high