Skip to content
Fencer Vulns
high 8.6

CVE-2024-1314 json

Kinto Attachment's attachments can be replaced on read-only records

published 2024-02-08 2 y ago modified 2026-07-07 4 mo ago also GHSA-hvp4-vrv2-8wrq , PYSEC-2026-1494

cvss
8.6
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

### 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

Patch / fix

  • pypi kinto-attachment 6.4.0

CVSS scores

assigned by version score vector
GitHub 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N
OSV 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
pypi kinto-attachment
<6.4.0
6.4.0

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.