Skip to content

Byobu user preference to prevent private discussions being started are not respected

Low severity GitHub Reviewed Published Jul 31, 2022 in FriendsOfFlarum/byobu • Updated Jul 21, 2023

Package

composer fof/byobu (Composer)

Affected versions

>= 0.3.0-beta.2, < 1.1.7

Patched versions

1.1.7

Description

Impact

Users electing to prevent others starting private discussions with themselves.

Please note that admins and others with appropriate permissions can always bypass this preference, as was the case before.

Patches

Users of Byobu should update the extension to version 1.1.7, where this has been patched. This version is only supported on v1.2.0 and later of Flarum Core.

Users of Byobu with Flarum 1.0 or 1.1 should upgrade to Flarum 1.2 or later, or evaluate the impact this issue has on your forum's users and choose to disable the extension if needed.

Workarounds

There are no workarounds for this issue.

References

@davwheat davwheat published to FriendsOfFlarum/byobu Jul 31, 2022
Published by the National Vulnerability Database Aug 1, 2022
Published to the GitHub Advisory Database Aug 6, 2022
Reviewed Aug 6, 2022
Last updated Jul 21, 2023

Severity

Low

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
Required
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:R/S:U/C:N/I:L/A:N

EPSS score

0.050%
(21st percentile)

Weaknesses

CVE ID

CVE-2022-35921

GHSA ID

GHSA-6gjm-6wj6-4px5

Source code

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