Sanitize sensitive headers and request bodies in JIRAError.__str__ to prevent credential leakage #2410
+57
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR addresses a security issue in
JIRAError.__str__where full request and response details are included in the exception string, including sensitive headers and potentially sensitive request bodies.When a JIRAError is logged, this can unintentionally leak:
This PR introduces sanitization logic to mask sensitive headers and redact potentially sensitive request body content before rendering the exception string.