ghsa-cr45-98w9-gwqx
Vulnerability from github
Published
2023-10-19 16:13
Modified
2024-11-18 16:26
Summary
Viewing wget extractor output while logged in as an admin allows archived JS to execute in the admins context
Details

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: https://github.com/ArchiveBox/ArchiveBox/issues/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

  • https://en.wikipedia.org/wiki/Cross-site_request_forgery
  • https://github.com/ArchiveBox/ArchiveBox#caveats
  • https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview
  • https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#security-concerns
Show details on source website


{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "archivebox"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "0.6.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2023-45815"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-79"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-10-19T16:13:50Z",
    "nvd_published_at": "2023-10-19T22:15:10Z",
    "severity": "HIGH"
  },
  "details": "### Impact\n\nAny users who are using the `wget` or `dom` extractors and view the content they output. \n\nThe 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. \n\nThe 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.\n\nBecause all of ArchiveBox\u0027s 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\u0027s usual CORS/CSRF security protections and leading to this issue.\n\n### Patches\n\nFollow here for progress on mitigating this issue: https://github.com/ArchiveBox/ArchiveBox/issues/239\n\n### Workarounds\n\nDisable the risky extractors by setting [`archivebox config --set SAVE_WGET=False SAVE_DOM=False`](https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#save_wget), 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.\n\n### References\n\n- https://en.wikipedia.org/wiki/Cross-site_request_forgery\n- https://github.com/ArchiveBox/ArchiveBox#caveats\n- https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview\n- https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#security-concerns",
  "id": "GHSA-cr45-98w9-gwqx",
  "modified": "2024-11-18T16:26:32Z",
  "published": "2023-10-19T16:13:50Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/security/advisories/GHSA-cr45-98w9-gwqx"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-45815"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/issues/239"
    },
    {
      "type": "WEB",
      "url": "https://en.wikipedia.org/wiki/Cross-site_request_forgery"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/ArchiveBox/ArchiveBox"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox#caveats"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/wiki/Configuration#save_wget"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#2-export-and-host-it-as-static-html"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/wiki/Publishing-Your-Archive#security-concerns"
    },
    {
      "type": "WEB",
      "url": "https://github.com/ArchiveBox/ArchiveBox/wiki/Security-Overview"
    },
    {
      "type": "WEB",
      "url": "https://github.com/pypa/advisory-database/tree/main/vulns/archivebox/PYSEC-2023-229.yaml"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Viewing wget extractor output while logged in as an admin allows archived JS to execute in the admins context"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...
  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.