Skip to content

Conversation

@chrismeyersfsu
Copy link
Member

@chrismeyersfsu chrismeyersfsu commented Jan 30, 2026

  • base64 encode user inputed url when logging so that newlines or other malicious payloads can't be injected into the log stream

Jira: https://issues.redhat.com/browse/AAP-63668

SUMMARY
ISSUE TYPE
  • Bug, Docs Fix or other nominal change
COMPONENT NAME
  • API
ADDITIONAL INFORMATION


Note

Low Risk
Changes are limited to log formatting around redirects plus additional unit coverage; runtime behavior for sending requests is unchanged aside from the logged message content.

Overview
Hardens webhook redirect logging by base64-encoding the current and next redirect URLs before emitting warning/error messages, reducing the risk of log injection from user-supplied URLs.

Adds unit tests covering redirect-follow behavior (successful redirect chain, missing Location header, and max-retry exhaustion) and ensures non-2xx responses (e.g., 404) are logged and treated as send failures when fail_silently is enabled.

Written by Cursor Bugbot for commit 6041b70. This will update automatically on new commits. Configure here.

@chrismeyersfsu chrismeyersfsu changed the title Harden log message output containing user input Jan 30, 2026
* base64 encode user inputed url when logging so that newlines or other
  malicious payloads can't be injected into the log stream
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

1 participant