NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · PyPI

CVE-2024-1314: Kinto Attachment's attachments can be replaced on read-only records

highCVSS 3.1 8.6GHSA-hvp4-vrv2-8wrq

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.

Published Feb 8, 2024

Affected packages

kinto-attachment

Ecosystem
PyPI
Affected
<= 6.3.2
Fixed in
6.4.0
Check
pip show kinto-attachment

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to Standard8, fkiriakos07, leplatrem.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology