Skip to content

docs: tie the control test to the THREAT_MODEL §8 properties - #2083

Merged
lukaszlenart merged 1 commit into
mainfrom
docs/control-test-threat-model-properties
Nov 2, 2026
Merged

lukaszlenart merged 1 commit into
mainfrom
docs/control-test-threat-model-properties

Conversation

@lukaszlenart

Copy link
Copy Markdown
Member

What

SECURITY.md carried 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.
  • The WW-5618 example is dated: when those limits were added the plugin promised no bound and §8.7 had not been written, so no control was claimed.
  • The "request-body size at the container" example in the no-control bullet contradicted §8.7 and is replaced by examples the framework genuinely leaves to the operator or application.
  • A third bullet writes down the WW-5642 precedent: a control still being extended across input channels is not broken on a channel it has not reached yet, and a gap there is public hardening with a no-regression requirement.

THREAT_MODEL.md already says all of this (§3, §8.7, §11a) and needs no change. Documentation only, no ticket.

🤖 Generated with Claude Code

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>
@lukaszlenart
lukaszlenart marked this pull request as ready for review October 31, 2026 13:16
@lukaszlenart
lukaszlenart merged commit 74af1ef into main Nov 2, 2026
5 checks passed
@lukaszlenart
lukaszlenart deleted the docs/control-test-threat-model-properties branch November 2, 2026 15:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant