Skip to content

Pimcore Admin Classic Bundle permissions are not getting checked when working with tags

Moderate severity GitHub Reviewed Published Feb 7, 2024 in pimcore/admin-ui-classic-bundle • Updated Feb 7, 2024

Package

composer pimcore/admin-ui-classic-bundle (Composer)

Affected versions

< 1.3.3

Patched versions

1.3.3

Description

Impact

You can create, delete etc. tags without having the permission to do so.
This vulnerability allows an attacker to perform broken access control and add tags to admin panel and add dumy data. One can do this as intruder and add text parameters with random numbers and this will effect integrity and availability.

Patches

Available in version 1.3.3.

Workarounds

Apply this pull request manually: pimcore/admin-ui-classic-bundle#412

References

References

@wisconaut wisconaut published to pimcore/admin-ui-classic-bundle Feb 7, 2024
Published by the National Vulnerability Database Feb 7, 2024
Published to the GitHub Advisory Database Feb 7, 2024
Reviewed Feb 7, 2024
Last updated Feb 7, 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
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:L/UI:N/S:U/C:N/I:H/A:N

EPSS score

0.059%
(26th percentile)

Weaknesses

CVE ID

CVE-2024-24822

GHSA ID

GHSA-3rfr-mpfj-2jwq

Source code

Credits

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