CVE-2024-27286

{
  "id": "CVE-2024-27286",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2024-27286",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "none"
            },
            {
              "automatable": "no"
            },
            {
              "technicalImpact": "partial"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2024-03-21T18:24:07.427438Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 6.5,
          "attackVector": "NETWORK",
          "baseSeverity": "MEDIUM",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
          "integrityImpact": "NONE",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "NONE",
          "privilegesRequired": "LOW",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 3.6,
        "exploitabilityScore": 2.8
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "zulip",
          "product": "zulip",
          "versions": [
            {
              "status": "affected",
              "version": ">= 3.0, < 8.3"
            }
          ]
        }
      ]
    }
  ],
  "published": "2024-03-20T20:15:08.407",
  "references": [
    {
      "url": "https://github.com/zulip/zulip/commit/3db1733310ddd944c2e690ba673232345c928eec",
      "tags": [
        "Patch"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/zulip/zulip/security/advisories/GHSA-478x-rfqr-w4jf",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/zulip/zulip/commit/3db1733310ddd944c2e690ba673232345c928eec",
      "tags": [
        "Patch"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    },
    {
      "url": "https://github.com/zulip/zulip/security/advisories/GHSA-478x-rfqr-w4jf",
      "tags": [
        "Third Party Advisory"
      ],
      "source": "af854a3a-2127-422b-91ae-364da2661108"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-200"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "Zulip is an open-source team collaboration tool. When a user moves a Zulip message, they have the option to move all messages in the topic, move only subsequent messages as well, or move just a single message.  If the user chose to just move one message, and was moving it from a public stream to a private stream, Zulip would successfully move the message, -- but active users who did not have access to the private stream, but whose client had already received the message, would continue to see the message in the public stream until they reloaded their client.  Additionally, Zulip did not remove view permissions on the message from recently-active users, allowing the message to show up in the \"All messages\" view or in search results, but not in \"Inbox\" or \"Recent conversations\" views. While the bug has been present since moving messages between streams was first introduced in version 3.0, this option became much more common starting in Zulip 8.0, when the default option in the picker for moving the very last message in a conversation was changed. This issue is fixed in Zulip Server 8.3. No known workarounds are available."
    },
    {
      "lang": "es",
      "value": "Zulip es una colaboración en equipo de código abierto. Cuando un usuario mueve un mensaje de Zulip, tiene la opción de mover todos los mensajes del tema, mover también solo los mensajes posteriores o mover solo un mensaje. Si el usuario elige mover solo un mensaje y lo mueve de una transmisión pública a una privada, Zulip movería exitosamente el mensaje, pero los usuarios activos que no tenían acceso a la transmisión privada, pero cuyo cliente ya lo había hecho. recibido el mensaje, continuaría viendo el mensaje en la transmisión pública hasta que recargaran su cliente. Además, Zulip no eliminó los permisos de visualización del mensaje de los usuarios activos recientemente, lo que permitió que el mensaje apareciera en la vista \"Todos los mensajes\" o en los resultados de búsqueda, pero no en las vistas \"Bandeja de entrada\" o \"Conversaciones recientes\". Si bien el error ha estado presente desde que se introdujo por primera vez el movimiento de mensajes entre transmisiones en la versión 3.0, esta opción se volvió mucho más común a partir de Zulip 8.0, cuando se cambió la opción predeterminada en el selector para mover el último mensaje de una conversación. Este problema se solucionó en Zulip Server 8.3. No hay workarounds disponibles. "
    }
  ],
  "lastModified": "2026-06-17T07:19:34.640",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:zulip:zulip_server:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "508FB61B-7BEF-4431-B276-EAE195ED4444",
              "versionEndExcluding": "8.3",
              "versionStartIncluding": "3.0"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}