CVE-2023-22489

Flarum is a discussion platform for websites. 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 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. 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. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.
Configurations

Configuration 1 (hide)

cpe:2.3:a:flarum:flarum:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:44

Type Values Removed Values Added
Summary
  • (es) Flarum es una plataforma de discusión para sitios web. Si la primera publicación de una discusión se elimina permanentemente pero la discusión permanece visible, cualquier actor que pueda ver la discusión podrá crear una nueva respuesta a través de la API REST, sin importar el permiso de respuesta o el estado de bloqueo. Esto incluye a los usuarios que no tienen un correo electrónico validado. Los invitados no pueden crear correctamente una respuesta porque la API fallará con un error 500 cuando se inserte el ID de usuario 0 en la base de datos. Esto sucede porque cuando la primera publicación de una discusión se elimina permanentemente, el atributo "first_post_id" de la discusión se vuelve "nulo", lo que hace que se omita el control de acceso para todas las respuestas nuevas. Flarum automáticamente hace invisibles las discusiones sin comentarios, por lo que una condición adicional para esta vulnerabilidad es que la discusión debe tener al menos una respuesta aprobada para que `discussions.comment_count` siga siendo superior a cero después de la eliminación de la publicación. Esto puede abrir la discusión a spam no controlado o simplemente a respuestas no intencionales si los usuarios todavía tenían su pestaña abierta antes de que se bloqueara la discusión vulnerable y luego publicar una respuesta cuando no deberían poder hacerlo. En combinación con la configuración de notificación por correo electrónico, esto también podría usarse como una forma de enviar correos electrónicos no solicitados. Las versiones entre `v1.3.0` y `v1.6.3` se ven afectadas. La vulnerabilidad ha sido reparada y publicada como flarum/core v1.6.3. Todas las comunidades que ejecutan Flarum deberían actualizar lo antes posible. No se conocen workarounds.
References () https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015 - Patch, Third Party Advisory () https://github.com/flarum/framework/commit/12f14112a0ecd1484d97330b82beb2a145919015 - Patch, Third Party Advisory
References () https://github.com/flarum/framework/releases/tag/v1.6.3 - Release Notes, Third Party Advisory () https://github.com/flarum/framework/releases/tag/v1.6.3 - Release Notes, Third Party Advisory
References () https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725 - Mitigation, Third Party Advisory () https://github.com/flarum/framework/security/advisories/GHSA-hph3-hv3c-7725 - Mitigation, Third Party Advisory

07 Nov 2023, 04:07

Type Values Removed Values Added
Summary Flarum is a discussion platform for websites. 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 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. 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. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds. Flarum is a discussion platform for websites. 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 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. 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. The vulnerability has been fixed and published as flarum/core v1.6.3. All communities running Flarum should upgrade as soon as possible. There are no known workarounds.

Information

Published : 2023-01-13 19:15

Updated : 2024-11-21 07:44


NVD link : CVE-2023-22489

Mitre link : CVE-2023-22489

CVE.ORG link : CVE-2023-22489


JSON object : View

Products Affected

flarum

  • flarum
CWE
CWE-862

Missing Authorization