CVE-2025-53106

Graylog is a free and open log management platform. In versions 6.2.0 to before 6.2.4 and 6.3.0-alpha.1 to before 6.3.0-rc.2, Graylog users can gain elevated privileges by creating and using API tokens for the local Administrator or any other user for whom the malicious user knows the ID. For the attack to succeed, the attacker needs a user account in Graylog. They can then proceed to issue hand-crafted requests to the Graylog REST API and exploit a weak permission check for token creation. This issue has been patched in versions 6.2.4 and 6.3.0-rc.2. A workaround involves disabling the respective configuration found in System > Configuration > Users > "Allow users to create personal access tokens".

CVSS

No CVSS.

References

Link	Resource
https://github.com/Graylog2/graylog2-server/commit/6936bd16a783c2944a3d2f1e83902062520f90e3
https://github.com/Graylog2/graylog2-server/commit/9215b8f1fd32566c31e6f7447ed864df3590c157
https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-3m86-c9x3-vwm9

Configurations

No configuration.

History

03 Jul 2025, 15:13

Type	Values Removed	Values Added
Summary		(es) Graylog es una plataforma de gestión de registros gratuita y abierta. En las versiones 6.2.0 y anteriores a la 6.2.4 y 6.3.0-alpha.1 y anteriores a la 6.3.0-rc.2, los usuarios de Graylog pueden obtener privilegios elevados mediante la creación y el uso de tokens de API para el administrador local o cualquier otro usuario cuyo ID conozca el usuario malicioso. Para que el ataque tenga éxito, el atacante necesita una cuenta de usuario en Graylog. Posteriormente, puede emitir solicitudes personalizadas a la API REST de Graylog y aprovechar una verificación de permisos deficiente para la creación de tokens. Este problema se ha corregido en las versiones 6.2.4 y 6.3.0-rc.2. Una solución alternativa consiste en deshabilitar la configuración correspondiente en Sistema > Configuración > Usuarios > "Permitir a los usuarios crear tokens de acceso personales".

02 Jul 2025, 14:15

Type	Values Removed	Values Added
New CVE

Information

Published : 2025-07-02 14:15

Updated : 2025-07-03 15:13

NVD link : CVE-2025-53106

Mitre link : CVE-2025-53106

CVE.ORG link : CVE-2025-53106

JSON object : View

Products Affected

No product.

CWE

CWE-285

Improper Authorization

{"id": "CVE-2025-53106", "cveTags": [], "metrics": {"cvssMetricV40": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 8.8, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "ACTIVE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "LOW", "subIntegrityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "integrityRequirement": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "subAvailabilityImpact": "HIGH", "vulnAvailabilityImpact": "HIGH", "availabilityRequirement": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "subConfidentialityImpact": "HIGH", "vulnConfidentialityImpact": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "vulnerabilityResponseEffort": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED"}}]}, "published": "2025-07-02T14:15:26.273", "references": [{"url": "https://github.com/Graylog2/graylog2-server/commit/6936bd16a783c2944a3d2f1e83902062520f90e3", "source": "security-advisories@github.com"}, {"url": "https://github.com/Graylog2/graylog2-server/commit/9215b8f1fd32566c31e6f7447ed864df3590c157", "source": "security-advisories@github.com"}, {"url": "https://github.com/Graylog2/graylog2-server/security/advisories/GHSA-3m86-c9x3-vwm9", "source": "security-advisories@github.com"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Primary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-285"}]}], "descriptions": [{"lang": "en", "value": "Graylog is a free and open log management platform. In versions 6.2.0 to before 6.2.4 and 6.3.0-alpha.1 to before 6.3.0-rc.2, Graylog users can gain elevated privileges by creating and using API tokens for the local Administrator or any other user for whom the malicious user knows the ID. For the attack to succeed, the attacker needs a user account in Graylog. They can then proceed to issue hand-crafted requests to the Graylog REST API and exploit a weak permission check for token creation. This issue has been patched in versions 6.2.4 and 6.3.0-rc.2. A workaround involves disabling the respective configuration found in System > Configuration > Users > \"Allow users to create personal access tokens\"."}, {"lang": "es", "value": "Graylog es una plataforma de gesti\u00f3n de registros gratuita y abierta. En las versiones 6.2.0 y anteriores a la 6.2.4 y 6.3.0-alpha.1 y anteriores a la 6.3.0-rc.2, los usuarios de Graylog pueden obtener privilegios elevados mediante la creaci\u00f3n y el uso de tokens de API para el administrador local o cualquier otro usuario cuyo ID conozca el usuario malicioso. Para que el ataque tenga \u00e9xito, el atacante necesita una cuenta de usuario en Graylog. Posteriormente, puede emitir solicitudes personalizadas a la API REST de Graylog y aprovechar una verificaci\u00f3n de permisos deficiente para la creaci\u00f3n de tokens. Este problema se ha corregido en las versiones 6.2.4 y 6.3.0-rc.2. Una soluci\u00f3n alternativa consiste en deshabilitar la configuraci\u00f3n correspondiente en Sistema > Configuraci\u00f3n > Usuarios > \"Permitir a los usuarios crear tokens de acceso personales\"."}], "lastModified": "2025-07-03T15:13:53.147", "sourceIdentifier": "security-advisories@github.com"}