GHSA-q7g5-jq6p-6wvx: Graylog's Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong value

Skip to content

Navigation Menu

• • GitHub Copilot

    Write better code with AI

  • GitHub Advanced Security

    Find and fix vulnerabilities

  • Actions

    Automate any workflow

  • Codespaces

    Instant dev environments

  • Issues

    Plan and track work

  • Code Review

    Manage code changes

  • Discussions

    Collaborate outside of code

  • Code Search

    Find more, search less

• Explore

  • Learning Pathways
  • Events & Webinars
  • Ebooks & Whitepapers
  • Customer Stories
  • Partners
  • Executive Insights

• • GitHub Sponsors

    Fund open source developers

*   The ReadME Project
    
    GitHub community articles

• • Enterprise platform

    AI-powered developer platform

• Pricing

Provide feedback

Saved searches****Use saved searches to filter your results more quickly

Sign up

1. GitHub Advisory Database
2. GitHub Reviewed
3. CVE-2025-30373

Graylog’s Authenticated HTTP inputs ingest message even if Authorization header is missing or has wrong value

Moderate severity GitHub Reviewed Published Apr 7, 2025 in Graylog2/graylog2-server • Updated Apr 7, 2025

Package

maven org.graylog2:graylog2-server (Maven)

Affected versions

>= 6.1.0, < 6.1.9

Description

Impact

Starting with 6.1, HTTP Inputs can be configured to check if a specified header is present and has a specified value to authenticate HTTP-based ingestion. Unfortunately, even though in cases of a missing header or a wrong value the correct HTTP response (401) is returned, the message will be ingested nonetheless.

Patches****Workarounds

Disabling http-based inputs and allow only authenticated pull-based inputs.

References****References

• GHSA-q7g5-jq6p-6wvx
• https://nvd.nist.gov/vuln/detail/CVE-2025-30373
• Graylog2/graylog2-server@31bc13d

Published to the GitHub Advisory Database

Apr 7, 2025

EPSS score