Skip to content

No permission checks for editing/deleting records with CSV import form

Moderate severity GitHub Reviewed Published Jan 23, 2024 in silverstripe/silverstripe-admin • Updated Jan 29, 2024

Package

composer silverstripe/admin (Composer)

Affected versions

>= 1.0.0, < 1.13.19
>= 2.0.0, < 2.1.8

Patched versions

1.13.19
2.1.8

Description

Impact

Users who don't have edit or delete permissions for records exposed in a ModelAdmin can still edit or delete records using the CSV import form, provided they have create permissions.

The likelyhood of a user having create permissions but not having edit or delete permissions is low, but it is possible.

Note that this doesn't affect any ModelAdmin which has had the import form disabled via the showImportForm public property, nor does it impact the SecurityAdmin section.

Action may be required

If you have a custom implementation of BulkLoader, you should update your implementation to respect permissions when the return value of getCheckPermissions() is true.

If you are using any BulkLoader in your own project logic, or maintain a module which uses it, you should consider passing true to setCheckPermissions() if the data is provided by users.

Base CVSS: 4.3
Reported by: Guy Sartorelli from Silverstripe

References

References

@GuySartorelli GuySartorelli published to silverstripe/silverstripe-admin Jan 23, 2024
Published by the National Vulnerability Database Jan 23, 2024
Published to the GitHub Advisory Database Jan 23, 2024
Reviewed Jan 23, 2024
Last updated Jan 29, 2024

Severity

Moderate

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
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:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.044%
(15th percentile)

Weaknesses

CVE ID

CVE-2023-49783

GHSA ID

GHSA-j3m6-gvm8-mhvw

Source code

Credits

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