GHSA-hph3-hv3c-7725

Suggest an improvement
Source
https://github.com/advisories/GHSA-hph3-hv3c-7725
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2023/01/GHSA-hph3-hv3c-7725/GHSA-hph3-hv3c-7725.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-hph3-hv3c-7725
Aliases
Published
2023-01-10T22:28:19Z
Modified
2023-11-08T04:11:36.542686Z
Severity
  • 3.5 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N CVSS Calculator
Summary
Any Flarum user including unactivated can reply in public discussions whose first post was permanently deleted
Details

If the first post of a discussion is permanently deleted but the discussion stays visible, any actor who can view the discussion is able to create a new reply via the REST API, no matter the reply permission or lock status.

This includes users that don't have a validated email.

Guests cannot successfully create a reply because the API will fail with a 500 error when the user ID 0 is inserted into the database. This should also be fixed to return the expected 401/403 status.

This happens because when the first post of a discussion is permanently deleted, the first_post_id attribute of the discussion becomes null which causes access control to be skipped for all new replies.

Flarum automatically makes discussions with zero comments invisible so an additional condition for this vulnerability is that the discussion must have at least one approved reply so that discussions.comment_count is still above zero after the post deletion.

Impact

This can open the discussion to uncontrolled spam or just unintentional replies if users still had their tab open before the vulnerable discussion was locked and then post a reply when they shouldn't be able to.

In combination with the email notification settings, this could also be used as a way to send unsolicited emails.

Versions between v1.3.0 and v1.6.3 are impacted.

Patches

The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible to v1.6.3 using:

composer update --prefer-dist --no-dev -a -W

You can then confirm you run the latest version using:

composer show flarum/core

Workarounds

If you don't delete the first posts you are not affected. A workaround can be to delete the discussion itself, or amend the database to manually set a first_post_id.

For more information

For any questions or comments on this vulnerability please visit https://discuss.flarum.org/

For support questions create a discussion at https://discuss.flarum.org/t/support.

A reminder that if you ever become aware of a security issue in Flarum, please report it to us privately by emailing security@flarum.org, and we will address it promptly.

Database specific 
{
    "nvd_published_at": "2023-01-13T19:15:00Z",
    "github_reviewed_at": "2023-01-10T22:28:19Z",
    "severity": "LOW",
    "github_reviewed": true,
    "cwe_ids": [
        "CWE-862"
    ]
}
References

Affected packages

Packagist / flarum/core

Package

Name
flarum/core
Purl
pkg:composer/flarum/core

Affected ranges

Type
ECOSYSTEM
Events
Introduced
1.3.0
Fixed
1.6.3

Affected versions

v1.*

v1.3.0
v1.3.1
v1.4.0
v1.4.1
v1.5.0
v1.6.0
v1.6.1
v1.6.2