* feat(#3415): ship local/no-unbounded-quantifier, burn down ReDoS class Phase 4 of epic #3212 (ADR-3212 §5/§7, the final phase). New rule flags an unbounded */+/{n,} quantifier over a broad character class ([\s\S], dotAll ., or a 1-2-unit negated class like [^\n]/[^)\n] — the exact #2128-fixed shape) applied to a regex whose match target is data-flow-traced to readFileSync content. eslint-rules/lib/readfilesync-trace.cjs extracts the data-flow tracer shared with no-crlf-fragile-split (Phase 2) rather than a second copy — no-crlf-fragile-split refactored onto it with zero behavior change, parity-tested. Real triage, not 798 mechanical edits: the ADR's census (2026-08-08) screened every unbounded quantifier in the tree unscoped. Correctly scoped to readFileSync-derived content (matching Phase 2's own G2/G3 scoping), the rule found 162 real hits across two detection waves — the second wave (93) surfaced only after a genuine off-by-one bug in this rule's own first draft was caught while writing its RuleTester tests and fixed (the bug silently missed every directly-quantified [\s\S]* with no gap before the quantifier — exactly the class this rule exists to catch). 3 hits landed in production src/ (commands.cts, milestone.cts, roadmap.cts) and were each empirically timed against adversarial input (matching #2128's own measured-not-assumed precedent) — all confirmed linear-time/benign, left unbounded with a measured-evidence comment rather than mechanically bounded. The remaining 159 are test-file fixture parsing (test-author-controlled, fixed-size content, not adversarial input) — each suppressed with a specific, non-generic reason. Zero functional behavior changed anywhere in this diff. tests/no-pending-3212-markers.test.cjs locks the epic's own closing invariant (ADR §7: "assert zero pending #3212 markers remain") — ground truth confirmed trivially true today (no phase left any such marker behind), now regression-locked going forward. Design: .gsd/phase/chore-3415-prohibition-with-teeth/40-design.md Test matrix: .gsd/phase/chore-3415-prohibition-with-teeth/50-test-matrix.md Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): correct rule category mislabel, add CI test-scope entry An orthogonal Standards-axis review found eslint-rules/no-unbounded-quantifier.cjs mistakenly carried meta.docs.category: 'Portability', copied from a sibling rule without realizing what that implied: docs/contributing/cross-platform- portability-rules.md governs an ADR-1703 rule family under a hard "zero escape hatches" contract (tests/portability-rule-disable-ban.test.cjs's PROTECTED_RULES bans eslint-disable for those rules entirely). This rule is not part of that family — it's ADR-3212 (ReDoS/CWE-1333), a different epic — and its eslint-disable-next-line suppressions (159 of them, added earlier this same phase after empirical benign-verification) are an intentional, correct design, not a bypass. Corrected to category: 'Best Practices', matching the actual precedent (no-adhoc-regex-escape.cjs, Phase 1 of the same epic, which is also correctly outside PROTECTED_RULES), and the rule's own docstring now states this explicitly so a future reader doesn't have to re-derive it. Also registers a new scripts/ci-test-scope.cjs bucket so editing this rule or the shared eslint-rules/lib/readfilesync-trace.cjs helper re-runs their own test suites under targeted CI selection — was previously unregistered and invisible to that fast-path (this PR's own gsd-test checkpoint runs the full suite regardless, so this only affects future narrowly-scoped PRs). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): bound no-unbounded-quantifier's own scanner (CWE-1333, ironic) Security review found the rule meant to catch algorithmic-complexity bugs had one of its own: hasUnboundedBroadQuantifier's negated-class inner scan walked from each `[^` occurrence to the next `]` (or EOF) with no bound, while the outer loop only ever advanced by one character — O(n²) total work on a pattern with many unclosed `[^` runs. Runs unconditionally inside checkPattern on any `new RegExp('literal string')` argument in any linted file, before the (cheap) readFileSync data-flow gate — so a single crafted string literal, no valid regex syntax required, could make `npm run lint` / CI hang. Empirically confirmed both the bug and the fix: pre-fix, n=4000/8000/ 16000/32000 chars took 30.8/115.6/463.8/1874.3ms (~4x work per 2x n, quadratic); extrapolated, the 300000-char repro from the finding would run ~165s. Post-fix (bail the inner scan once units exceeds the rule's own 1-2-unit scope, rather than continuing to hunt for a closing `]`), the same 300000-char input runs in 8.7ms via the real rule module, independently reconfirmed at 18ms via a fresh Linter.verify() call. New regression row in tests/no-unbounded-quantifier.rule.test.cjs asserts the RuleTester run on a 50000-char adversarial pattern completes and returns a defined result — no wall-clock assertion (CLAUDE.md Clock Seams / local/no-elapsed-assertion). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * fix(#3415): triage 3 new sites, re-raise ceiling after upstream batch next merged 12 more PRs during this PR's review. Two consequences: - tests/edit-phase.test.cjs (fix #3262, unrelated) added 3 new content.match(/<tag>([\s\S]*?)<\/tag>/) reads of this repo's own workflow .md content — the same Class A pattern as the ~159 sites already triaged elsewhere in this PR. Suppressed with the same established reason. - lint-allow-test-rule-refs' ratchet ceiling needed re-raising again (301 -> 303) for the same reason as the two prior bumps: organic growth from unrelated, already-reviewed PRs landing concurrently, not a defect in this branch's own diff. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
146 lines
5.7 KiB
JavaScript
146 lines
5.7 KiB
JavaScript
'use strict';
|
|
|
|
/**
|
|
* readfilesync-trace-parity.test.cjs
|
|
*
|
|
* Row 14 of .gsd/phase/chore-3415-prohibition-with-teeth/50-test-matrix.md:
|
|
* `no-crlf-fragile-split.cjs` and `no-unbounded-quantifier.cjs` both import
|
|
* their readFileSync-derivation data-flow tracing from the shared
|
|
* `eslint-rules/lib/readfilesync-trace.cjs` module (extracted from
|
|
* no-crlf-fragile-split, ADR-1703 Phase 4 / ADR-3212 §5-6, #3415). There is
|
|
* no separate "pre-extraction inline copy" left to diff against — this test
|
|
* instead asserts the two RULES currently AGREE on the shared data-flow
|
|
* classification: for a fixture whose receiver is NOT readFileSync-derived,
|
|
* BOTH rules must report zero errors, even though each rule's own
|
|
* pattern-shape condition (bare `\n` for crlf; broad-atom + unbounded
|
|
* quantifier for unbounded-quantifier) would independently match the regex
|
|
* content. For a fixture whose receiver IS readFileSync-derived (direct,
|
|
* chained, or via a same-scope variable), each rule's own pattern-shape
|
|
* condition is ALSO satisfied by every fixture below, so each fires.
|
|
*
|
|
* `isPatternUsedOnFileContent`/`isReadFileSyncDerived` are not exercised
|
|
* standalone: both take a live `sourceCode` (parent pointers via
|
|
* `sourceCode.getScope`/`node.parent`) that only exists inside a real
|
|
* ESLint visitor, so a RuleTester run against both consuming rules is the
|
|
* faithful way to exercise the shared module identically to production.
|
|
*/
|
|
|
|
const { test, describe } = require('node:test');
|
|
const assert = require('node:assert/strict');
|
|
const { RuleTester } = require('eslint');
|
|
|
|
const crlfRule = require('../eslint-rules/no-crlf-fragile-split.cjs');
|
|
const quantifierRule = require('../eslint-rules/no-unbounded-quantifier.cjs');
|
|
const trace = require('../eslint-rules/lib/readfilesync-trace.cjs');
|
|
|
|
const ruleTester = new RuleTester({
|
|
languageOptions: {
|
|
ecmaVersion: 2022,
|
|
sourceType: 'commonjs',
|
|
},
|
|
});
|
|
|
|
// ─── shared module shape ────────────────────────────────────────────────────
|
|
|
|
describe('readfilesync-trace shared module shape', () => {
|
|
test('exports isReadFileSyncDerived(node, sourceCode) and isPatternUsedOnFileContent(regexNode, sourceCode)', () => {
|
|
assert.strictEqual(typeof trace.isReadFileSyncDerived, 'function');
|
|
assert.strictEqual(trace.isReadFileSyncDerived.length, 2);
|
|
assert.strictEqual(typeof trace.isPatternUsedOnFileContent, 'function');
|
|
assert.strictEqual(trace.isPatternUsedOnFileContent.length, 2);
|
|
});
|
|
});
|
|
|
|
// ─── shared fixtures ─────────────────────────────────────────────────────────
|
|
//
|
|
// Every fixture's regex carries BOTH a bare \n (crlf rule's own pattern-shape
|
|
// trigger) AND an unbounded [\s\S]* (unbounded-quantifier rule's own
|
|
// pattern-shape trigger), so any divergence between the two rules can only
|
|
// come from disagreement on the shared readFileSync-derived classification,
|
|
// never from a pattern-shape mismatch.
|
|
|
|
const READFILESYNC_DERIVED_FIXTURES = [
|
|
{
|
|
name: 'direct call: fs.readFileSync(p, "utf8").match(...)',
|
|
code: "const m = fs.readFileSync(p, 'utf8').match(/[\\s\\S]*\\n/);",
|
|
},
|
|
{
|
|
name: 'chained call: fs.readFileSync(p, "utf8").toString().match(...)',
|
|
code: "const m = fs.readFileSync(p, 'utf8').toString().match(/[\\s\\S]*\\n/);",
|
|
},
|
|
{
|
|
name: 'scope variable: const content = fs.readFileSync(...); content.match(...)',
|
|
code: [
|
|
"const content = fs.readFileSync(filePath, 'utf8');",
|
|
'const m = content.match(/[\\s\\S]*\\n/);',
|
|
].join('\n'),
|
|
},
|
|
];
|
|
|
|
const NOT_READFILESYNC_DERIVED_FIXTURES = [
|
|
{
|
|
name: 'plain identifier: someShortConstant.match(...)',
|
|
code: 'const m = someShortConstant.match(/[\\s\\S]*\\n/);',
|
|
},
|
|
{
|
|
name: 'scope variable NOT from readFileSync: const content = "hello"; content.match(...)',
|
|
code: ["const content = 'hello';", 'const m = content.match(/[\\s\\S]*\\n/);'].join('\n'),
|
|
},
|
|
];
|
|
|
|
// ─── parity: readFileSync-derived receivers — both rules fire ───────────────
|
|
|
|
describe('readfilesync-trace parity: readFileSync-derived receivers — both rules fire', () => {
|
|
for (const fixture of READFILESYNC_DERIVED_FIXTURES) {
|
|
test(`crlf and unbounded-quantifier both fire on: ${fixture.name}`, () => {
|
|
ruleTester.run('no-crlf-fragile-split', crlfRule, {
|
|
valid: [],
|
|
invalid: [
|
|
{
|
|
code: fixture.code,
|
|
filename: 'tests/foo.test.cjs',
|
|
errors: [{ messageId: 'crlfFragileRegex' }],
|
|
},
|
|
],
|
|
});
|
|
ruleTester.run('no-unbounded-quantifier', quantifierRule, {
|
|
valid: [],
|
|
invalid: [
|
|
{
|
|
code: fixture.code,
|
|
filename: 'tests/foo.test.cjs',
|
|
errors: [{ messageId: 'unboundedQuantifier' }],
|
|
},
|
|
],
|
|
});
|
|
});
|
|
}
|
|
});
|
|
|
|
// ─── parity: non-readFileSync-derived receivers — both rules stay silent ────
|
|
|
|
describe('readfilesync-trace parity: non-readFileSync-derived receivers — both rules agree on zero', () => {
|
|
for (const fixture of NOT_READFILESYNC_DERIVED_FIXTURES) {
|
|
test(`crlf and unbounded-quantifier both report zero on: ${fixture.name}`, () => {
|
|
ruleTester.run('no-crlf-fragile-split', crlfRule, {
|
|
valid: [
|
|
{
|
|
code: fixture.code,
|
|
filename: 'tests/foo.test.cjs',
|
|
},
|
|
],
|
|
invalid: [],
|
|
});
|
|
ruleTester.run('no-unbounded-quantifier', quantifierRule, {
|
|
valid: [
|
|
{
|
|
code: fixture.code,
|
|
filename: 'tests/foo.test.cjs',
|
|
},
|
|
],
|
|
invalid: [],
|
|
});
|
|
});
|
|
}
|
|
});
|