Graylog2__graylog2-server_CVE-2023-41044_5-1-2

Graylog 환영합니다! Graylog는 오픈 소스 로그 관리 플랫폼입니다. 프로젝트에 대한 자세한 내용은 웹사이트에서, 문서는 문서 사이트에서 확인하실 수 있습니다. 이슈 트래킹 버그를 발견하셨나요? 개선 아이디어가 있으신가요? 부담 없이 이슈를 등록해 주세요. 기여하기 로그 관리의 미래를 함께 만들고, 매일 수천 명의 사람들이 사용하는 프로젝트에 참여해 보세요. 기여자 가이드를 확인하고 기여 지침을 읽어 시작하세요. 오픈 소스 제품 개발에 대한 보상을 받고 싶으신가요? 채용 공고에 지원해 보세요! 연락 유지하기 grayl...

CVE-2026-65011

Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/definitionId/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private...

CVE-2026-65011 Graylog2 Server Missing Permission Check on Event Definition Duplicate

Graylog2 Server before commit 46a2eeb contains a missing per-entity permission check in the POST /events/definitions/definitionId/duplicate endpoint that allows authenticated users to clone any event definition. Attackers with the low-privilege eventdefinitions:create capability can read private...

CVE-2026-65011

Technical details are not publicly available in the provided documents. Monitor for updates.

Cross-site Scripting (XSS)

org.graylog2:graylog2-server is vulnerable to Cross-site Scripting XSS. The vulnerability is due to insecure input handling due to the ability to inject and submit malicious HTML forms via the Event Definition Remediation Step field, which can result in session cookie theft under specific...

Authentication Bypass

org.graylog2, graylog2-server is vulnerable to Authentication Bypass. The vulnerability is due to HTTP Inputs not correctly rejecting messages when a specified header is missing or has an incorrect value, allowing the message to be ingested despite returning a 401 HTTP response...

DNS Cache Poisoning

graylog2-server is vulnerable to DNS Cache Poisoning. The vulnerability exists because the library uses a single source port for DNS queries, leading to cache poisoning attacks...

Session Fixation

graylog2-server is vulnerable to Session Fixation. The vulnerability exists because a node may still have the session cached even when a user has explicitly logged out, which allows the session to still be used for API requests until it has reached its original expiry time...