Skip to content

Cachet vulnerable to forced reinstall

High severity GitHub Reviewed Published Aug 27, 2021 in fiveai/Cachet • Updated Jan 28, 2023

Package

composer cachethq/cachet (Composer)

Affected versions

< 2.5.1

Patched versions

2.5.1

Description

Impact

Authenticated users, regardless of their privileges (User or Admin), can trick Cachet and install the instance again, leading to arbitrary code execution on the server.

Patches

This issue was addressed by improving the middleware ReadyForUse, which now performs a stricter validation of the instance name.

Workarounds

Only allow trusted source IP addresses to access to the administration dashboard.

References

For more information

If you have any questions or comments about this advisory, you can contact:

  • The original reporters, by sending an email to vulnerability.research [at] sonarsource.com;
  • The maintainers, by opening an issue on this repository.

References

@sedan07 sedan07 published to fiveai/Cachet Aug 27, 2021
Published by the National Vulnerability Database Aug 27, 2021
Reviewed Aug 27, 2021
Published to the GitHub Advisory Database Aug 30, 2021
Last updated Jan 28, 2023

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:H/I:H/A:H

EPSS score

0.912%
(83rd percentile)

Weaknesses

CVE ID

CVE-2021-39173

GHSA ID

GHSA-r67m-m8c7-jp83

Source code

Credits

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