Skip to content

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

High severity GitHub Reviewed Published Feb 8, 2024 in Kinto/kinto-attachment • Updated Feb 8, 2024

Package

pip kinto-attachment (pip)

Affected versions

<= 6.3.2

Patched versions

6.4.0

Description

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

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

References

@leplatrem leplatrem published to Kinto/kinto-attachment Feb 8, 2024
Published to the GitHub Advisory Database Feb 8, 2024
Reviewed Feb 8, 2024
Last updated Feb 8, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:N

EPSS score

Weaknesses

No CWEs

CVE ID

CVE-2024-1314

GHSA ID

GHSA-hvp4-vrv2-8wrq

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.