pysec-2024-15
Vulnerability from pysec
Published
2024-01-19 20:15
Modified
2024-01-26 22:21
Details

changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint /api/v1/watch/<uuid>/history can be accessed by any unauthorized user. As a result any unauthorized user can check one's watch history. However, because unauthorized party first needs to know a watch UUID, and the watch history endpoint itself returns only paths to the snapshot on the server, an impact on users' data privacy is minimal. This issue has been addressed in version 0.45.13. Users are advised to upgrade. There are no known workarounds for this vulnerability.




{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "changedetection-io",
        "purl": "pkg:pypi/changedetection-io"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "402f1e47e78ecd155b1e90f30cce424ff7763e0f"
            }
          ],
          "repo": "https://github.com/dgtlmoon/changedetection.io",
          "type": "GIT"
        },
        {
          "events": [
            {
              "introduced": "0.39.14"
            },
            {
              "fixed": "0.45.13"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "0.39.14",
        "0.39.14.1",
        "0.39.15",
        "0.39.16",
        "0.39.17",
        "0.39.17.1",
        "0.39.17.2",
        "0.39.18",
        "0.39.19",
        "0.39.19.1",
        "0.39.20",
        "0.39.20.1",
        "0.39.20.2",
        "0.39.20.3",
        "0.39.20.4",
        "0.39.21",
        "0.39.21.1",
        "0.39.22",
        "0.39.22.1",
        "0.40.0",
        "0.40.0.1",
        "0.40.0.2",
        "0.40.0.3",
        "0.40.0.4",
        "0.40.1.0",
        "0.40.1.1",
        "0.40.2",
        "0.40.3",
        "0.41",
        "0.41.1",
        "0.42",
        "0.42.1",
        "0.42.2",
        "0.42.3",
        "0.43.1",
        "0.43.2",
        "0.44",
        "0.44.1",
        "0.45",
        "0.45.1",
        "0.45.11",
        "0.45.12",
        "0.45.2",
        "0.45.3",
        "0.45.4",
        "0.45.5",
        "0.45.6",
        "0.45.7",
        "0.45.7.1",
        "0.45.7.2",
        "0.45.7.3",
        "0.45.8",
        "0.45.8.1",
        "0.45.9"
      ]
    }
  ],
  "aliases": [
    "CVE-2024-23329",
    "GHSA-hcvp-2cc7-jrwr"
  ],
  "details": " changedetection.io is an open source tool designed to monitor websites for content changes. In affected versions the API endpoint `/api/v1/watch/\u003cuuid\u003e/history` can be accessed by any unauthorized user. As a result any unauthorized user can check one\u0027s watch history. However, because unauthorized party first needs to know a watch UUID, and the watch history endpoint itself returns only paths to the snapshot on the server, an impact on users\u0027 data privacy is minimal. This issue has been addressed in version 0.45.13. Users are advised to upgrade. There are no known workarounds for this vulnerability.",
  "id": "PYSEC-2024-15",
  "modified": "2024-01-26T22:21:10.756741+00:00",
  "published": "2024-01-19T20:15:00+00:00",
  "references": [
    {
      "type": "EVIDENCE",
      "url": "https://github.com/dgtlmoon/changedetection.io/security/advisories/GHSA-hcvp-2cc7-jrwr"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/dgtlmoon/changedetection.io/security/advisories/GHSA-hcvp-2cc7-jrwr"
    },
    {
      "type": "FIX",
      "url": "https://github.com/dgtlmoon/changedetection.io/commit/402f1e47e78ecd155b1e90f30cce424ff7763e0f"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • 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.