GHSA-HVP4-VRV2-8WRQ

Vulnerability from github – Published: 2024-02-08 18:32 – Updated: 2024-02-08 18:32
VLAI
Summary
Kinto Attachment's attachments can be replaced on read-only records
Details

Impact

The attachment file of an existing record can be replaced if the user has "read" permission on one of the parent (collection or bucket).

And if the "read" permission is given to "system.Everyone" on one of the parent, then the attachment can be replaced on a record using an anonymous request.

Note that if the parent has no explicit read permission, then the records attachments are safe.

Patches

  • Patch released in kinto-attachment 6.4.0
  • https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1

Workarounds

None if the read permission has to remain granted.

Updating to 6.4.0 or applying the patch individually (if updating is not feasible) is strongly recommended.

References

  • https://bugzilla.mozilla.org/show_bug.cgi?id=1879034
Severity
8.6 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 6.3.2"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "kinto-attachment"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "6.4.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2024-1314"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": true,
    "github_reviewed_at": "2024-02-08T18:32:10Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "### Impact\n\nThe attachment file of an existing record can be replaced if the user has `\"read\"` permission on one of the parent (collection or bucket).\n\nAnd if the `\"read\"` permission is given to `\"system.Everyone\"` on one of the parent, then the attachment can be replaced on a record using an anonymous request.\n\nNote that if the parent has no explicit read permission, then the records attachments are safe.\n\n### Patches\n\n- Patch released in kinto-attachment 6.4.0\n- https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1\n\n### Workarounds\n\nNone if the read permission has to remain granted.\n\nUpdating to 6.4.0 or applying the patch individually (if updating is not feasible) is strongly recommended.\n\n### References\n\n- https://bugzilla.mozilla.org/show_bug.cgi?id=1879034",
  "id": "GHSA-hvp4-vrv2-8wrq",
  "modified": "2024-02-08T18:32:10Z",
  "published": "2024-02-08T18:32:10Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/Kinto/kinto-attachment/security/advisories/GHSA-hvp4-vrv2-8wrq"
    },
    {
      "type": "WEB",
      "url": "https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.mozilla.org/show_bug.cgi?id=1879034"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/Kinto/kinto-attachment"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Kinto Attachment\u0027s attachments can be replaced on read-only records"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.