CVE-2024-1314:
Kinto Attachment's attachments can be replaced on read-only records
8.6
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
-
CWE
-
Published
2/8/2024
Updated
2/8/2024
KEV Status
No
Technology
Python
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
kinto-attachment | pip | <= 6.3.2 | 6.4.0 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stemmed from improper authorization context handling in AttachmentRouteFactory. The pre-patch code didn't set 'self.current_object = existing' when records existed, which is critical for Kinto's authorization policy to distinguish between collection-level and record-level operations. This caused the system to check create permissions on the parent collection (which might be granted via read inheritance) instead of requiring write permissions on the existing record. The patch explicitly sets the current_object context and adds security-focused test cases to validate this behavior.