Skip to content

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

Patched versions

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

@dennisoelkers dennisoelkers published to Graylog2/graylog2-server Apr 7, 2025
Published by the National Vulnerability Database Apr 7, 2025
Published to the GitHub Advisory Database Apr 7, 2025
Reviewed Apr 7, 2025
Last updated Apr 7, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(2nd percentile)

Weaknesses

CVE ID

CVE-2025-30373

GHSA ID

GHSA-q7g5-jq6p-6wvx

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.