PyPI: kinto-attachment
CVE-2024-1314
Safety vulnerability ID: SFTY-20240315-02837
Safety legacy ID: pyup.io-66714
kinto-attachment versions above 6.4.0 are susceptible to a vulnerability where an attachment file on an existing record can be replaced by users who possess "read" permission on any of the parent entities, such as a collection or bucket. Should this "read" permission be granted to "system.Everyone" on one of the parents, it enables the replacement of an attachment on a record through an anonymous request. Importantly, should the parent entities not have explicit "read" permission assigned, the attachments on records remain secure against such unauthorized replacements.
Overview
Kinto Attachment's attachments can be replaced on read-only records
Advisory
kinto-attachment versions above 6.4.0 are susceptible to a vulnerability where an attachment file on an existing record can be replaced by users who possess "read" permission on any of the parent entities, such as a collection or bucket. Should this "read" permission be granted to "system.Everyone" on one of the parents, it enables the replacement of an attachment on a record through an anonymous request. Importantly, should the parent entities not have explicit "read" permission assigned, the attachments on records remain secure against such unauthorized replacements.
How to Fix
Mitigation and Workarounds
---
Vulnerable Functions
Functions linked to known vulnerabilities.
References
- https://getsafety.com/vulnerabilities/SFTY-20240315-02837/CVE-2024-1314
- https://github.com/Kinto/kinto-attachment/security/advisories/GHSA-hvp4-vrv2-8wrq
- https://github.com/Kinto/kinto-attachment/commit/f4a31484f5925cbc02b59ebd37554538ab826ca1
- https://bugzilla.mozilla.org/show_bug.cgi?id=1879034
- https://github.com/advisories/GHSA-hvp4-vrv2-8wrq
Verified by Safety
Our Cybersecurity Intelligence Team reviewed this vulnerability. We combine public data with our own research to find issues not yet reported to public sources.
Learn more
