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.
Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd
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.
Analysis provided by Fabian Yamaguchi - Whirly Labs (Pty) Ltd