Update triage state with issue #18 security bug analysis#43
Open
BodenMcHale wants to merge 1 commit into
Open
Conversation
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
2 participants
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.
Summary
Updated the triage state tracking file to record the latest triage run and document the analysis of issue #18, a security bug related to the
no-referrer-when-downgradepolicy in the CSP rules.Changes
last_runtimestamp to 2026-05-26T05:45:00Zlast_commithash to reflect the latest commitno-referrer-when-downgradeclassified as "strong" — awards full score for the historical browser default that leaks full URLs cross-origin #18:no-referrer-when-downgradeinstrongValuesat src/rules.ts:113unsafe-none/cross-originget full credit #8, and [REVIEW] Permissions-Policy tests: 4 assertions broken by merge regression — main branch CI is red #15:unsafe-none/cross-originget full credit #8 deprioritized in favor of [REVIEW] Referrer-Policy:no-referrer-when-downgradeclassified as "strong" — awards full score for the historical browser default that leaks full URLs cross-origin #18 (security bug with fewer comments)no-referrer-when-downgradeclassified as "strong" — awards full score for the historical browser default that leaks full URLs cross-origin #18 (security bug, Priority 1)Implementation Details
The triage state now reflects a prioritization decision where issue #18 was selected as the top candidate for action due to its security classification and lower comment count compared to other open issues. The fix involves removing a potentially problematic referrer policy from the strong values list and updating corresponding test assertions.
https://claude.ai/code/session_01FnCagxV2wEg8X1nHtX9uwC