CVE-2025-46827

{"id": "CVE-2025-46827", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.0, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "REQUIRED", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.1}]}, "published": "2025-05-07T16:15:22.720", "references": [{"url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-76vf-mpmx-777j", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-79"}]}], "descriptions": [{"lang": "en", "value": "Graylog is a free and open log management platform. Prior to versions 6.0.14, 6.1.10, and 6.2.0, it is possible to obtain user session cookies by submitting an HTML form as part of an Event Definition Remediation Step field. For this attack to succeed, the attacker needs a user account with permissions to create event definitions, while the user must have permissions to view alerts. Additionally, an active Input must be present on the Graylog server that is capable of receiving form data (e.g. a HTTP input, TCP raw or syslog etc). Versions 6.0.14, 6.1.10, and 6.2.0 fix the issue. No known workarounds are available, as long as the relatively rare prerequisites are met."}, {"lang": "es", "value": "Graylog es una plataforma de gesti\u00f3n de registros gratuita y abierta. En versiones anteriores a las 6.0.14, 6.1.10 y 6.2.0, era posible obtener cookies de sesi\u00f3n de usuario enviando un formulario HTML como parte de un campo de Paso de Remediaci\u00f3n de Definici\u00f3n de Evento. Para que este ataque tenga \u00e9xito, el atacante necesita una cuenta de usuario con permisos para crear definiciones de eventos, y el usuario debe tener permisos para ver alertas. Adem\u00e1s, debe existir una entrada activa en el servidor Graylog capaz de recibir datos del formulario (por ejemplo, una entrada HTTP, TCP sin procesar o syslog, etc.). Las versiones 6.0.14, 6.1.10 y 6.2.0 solucionan el problema. No se conocen workarounds, siempre que se cumplan los prerrequisitos, relativamente poco frecuentes."}], "lastModified": "2025-05-08T14:39:09.683", "sourceIdentifier": "security-advisories@github.com"}