Conversation
ConfirmManagerChange logged token[:8]+"..." in five places without a length guard, so any confirmation token shorter than 8 characters triggered a slice-out-of-bounds panic. middleware.Recover turned that panic into a 500, masking the intended 400 for an invalid token. Guard every log site with token[:min(len(token), 8)] and un-skip the integration regression test, which now drives ConfirmManagerChange with a short token and a long bogus token through a struct table, asserting a 400 and the "Invalid or expired confirmation token" body in both cases.
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
ConfirmManagerChange logged token[:8]+"..." in five places without a
length guard, so any confirmation token shorter than 8 characters
triggered a slice-out-of-bounds panic. middleware.Recover turned that
panic into a 500, masking the intended 400 for an invalid token.
Guard every log site with token[:min(len(token), 8)] and un-skip the
integration regression test, which now drives ConfirmManagerChange with
a short token and a long bogus token through a struct table, asserting a
400 and the "Invalid or expired confirmation token" body in both cases.