Skip to content

Potential unauthorized access to stored request & session data when plugin is misconfigured in October CMS Debugbar

Moderate severity GitHub Reviewed Published Jun 1, 2020 in rainlab/debugbar-plugin • Updated Jan 9, 2023

Package

composer rainlab/debugbar-plugin (Composer)

Affected versions

< 3.1.0

Patched versions

3.1.0

Description

Impact

The debugbar contains a perhaps little known feature where it will log all requests (and all information pertaining to each request including session data) whenever it is enabled. This presents a problem if the plugin is ever enabled on a system that is open to untrusted users as the potential exists for them to use this feature to view all requests being made to the application and obtain sensitive information from those requests. There even exists the potential for account takeovers of authenticated users by non-authenticated public users, which would then lead to a number of other potential issues as an attacker could theoretically get full access to the system if the required conditions existed.

Patches

Issue has been patched in v3.1.0 by locking down access to the debugbar to all users; it now requires an authenticated backend user with a specifically enabled permission before it is even usable, and the feature that allows access to stored request information is restricted behind a different permission that's more restrictive.

Workarounds

Apply rainlab/debugbar-plugin@86dd29f to your installation manually if unable to upgrade to v3.1.0.

For more information

If you have any questions or comments about this advisory:

Acknowledgements

Thanks to Freddie Poser for reporting the issue to the RainLab team.

References

@LukeTowers LukeTowers published to rainlab/debugbar-plugin Jun 1, 2020
Reviewed Jun 3, 2020
Published to the GitHub Advisory Database Jun 3, 2020
Last updated Jan 9, 2023

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
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
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:H/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.342%
(72nd percentile)

Weaknesses

CVE ID

CVE-2020-11094

GHSA ID

GHSA-c8wh-6jw4-2h79

Source code

No known source code

Credits

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