Skip to content

Leaking fields if the request fields where empty or only fields selected where not populatable

Moderate
Boegie19 published GHSA-6h67-934r-82g7 Nov 20, 2023

Package

npm strapi-plugin-protected-populate (npm)

Affected versions

1.3.3

Patched versions

1.3.4

Description

Impact

people where able to bypass the field level security. This means fields that they where not allowed to populate could be populate anyway. If they tried to populate something that they don't have access to.

Patches

This issue has been patched in 1.3.4

Workarounds

None

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

CVE ID

CVE-2023-48218

Weaknesses

No CWEs