CVE-2024-1314
Published:August 19, 2025
Updated:July 08, 2026
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
Affected Packages
kinto-attachment (PYTHON):
Affected version(s) >=0.1.0 <6.4.0Fix Suggestion:
Update to version 6.4.0Related Resources (7)
Do you need more information?
Contact UsCVSS v4
Base Score:
9.2
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
HIGH
Subsequent System Availability
NONE
CVSS v3
Base Score:
8.6
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
EPSS
Base Score:
0.70