Repository navigation
docs: tie the control test to the THREAT_MODEL §8 properties - #2083
Merged
Merged
Conversation
SECURITY.md said both that an unbounded read of request-derived input is in scope even when linear, and that a bound the framework never promised is hardening. For a read with no documented limit the two passages gave different answers, while S2-073 and S2-077 had already been handled as vulnerabilities. State what reconciles them: THREAT_MODEL §8.7 promises bounded consumption, and a §8 property is a claimed control for the purposes of the control test. Date the WW-5618 example accordingly (no bound promised, §8.7 not yet written), replace the container body-size example that contradicted §8.7, and write down the WW-5642 precedent for a control that is still being extended across input channels. Co-Authored-By: Claude Mythos 5.1 <noreply@anthropic.com>
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
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.
What
SECURITY.mdcarried two statements that disagree for one case. Line 51 says framework code that reads or retains request-derived input without any bound is in scope even when the growth is linear. The control test two paragraphs later says a bound the framework never promised is hardening with no CVE. An unbounded read with no documented limit falls under both, and the project has already handled that case as a vulnerability (S2-073, S2-077).This change states the reconciliation instead of leaving it implied:
THREAT_MODEL.md§8.7 promises bounded consumption of request-derived input, and a §8 property counts as a claimed control for the control test. That is why an unbounded read is a vulnerability today.THREAT_MODEL.mdalready says all of this (§3, §8.7, §11a) and needs no change. Documentation only, no ticket.🤖 Generated with Claude Code