mirror of
https://github.com/elicpeter/nyx.git
synced 2026-06-09 19:45:13 +02:00
* feat: Introduce function-scoped variable interning for state analysis with new tests and fixtures * feat: Add Phase 26 symbolic execution enhancements with bitwise operator support, abstract interpretation refinements, and new taint analysis tests * feat: Refine state analysis to handle factory-pattern resource returns with mixed-path tests and leak detection enhancements * feat: Add Phase 27 debug views with symbolic execution, abstract interpretation, SSA, and call graph viewers; integrate with debug layout and styles * feat: Add Phase 31 type-qualified symbolic resolution with receiver-based callee disambiguation and testing * feat: Extend symbolic execution with state iteration, enhanced debug views, and debounced input handling * feat: Add Phase 13 resource and auth pattern extensions with new tests and fixtures * feat: Introduce CFG debug graph renderer with compact mode, toolbar, and DAG layout integration * feat: Add Phase 28 encoding and decoding transform modeling with structural symex enhancements and new taint analysis tests * feat: Extend abstract interpretation with type facts and constant value tracking in debug views and server logic * feat: Add linear path handling and witness extraction to symbolic execution with Phase 28 transform mismatch detection * feat: Refine Go auth and sanitizer handling with enhanced rules, state updates, and benchmark improvements * feat: Enable auth-state analysis by default and update relevant tests in benchmark config * test: Update state_tests to reflect default enablement of auth-state analysis and add auth suppression test * docs: update CHANGELOG.md * feat: Introduce per-index taint tracking in `HeapState` with `HeapSlot`, overflow handling, and revised SSA transfers * feat: Introduce C/C++ language labels and refine heap state tracking in SSA transfers * feat: Implement per-index array slot tracking in symbolic heap with overflow collapse * feat: Add implicit definition handling for uninitialized declarations in SSA value allocation * feat: Refactor function parameters and constants for improved clarity and maintainability * refactor: Reorder module imports and improve formatting for consistency * refactor: Fix formatting erorrs * refactor: Fix clippy warnings * refactor: Fix fmt warnings (again) * chore: Update dependencies and improve feature configuration * Add comprehensive tests for undertested modules (#36) (COPILOT) * Add comprehensive tests for undertested modules Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/f3fc877e-f386-49ba-9793-fc93d3805083 * Add comprehensive tests for ext, project, walk, and errors modules Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/f3fc877e-f386-49ba-9793-fc93d3805083 --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * chore: Update dependencies and improve feature configuration * fix: formatting errors in new tests * chore: Update license list in about.toml * chore: made functions input inline * chore: updated cfg graph to take up the full page * chore: add Prettier configuration and update code formatting * Add frontend test suite with Vitest (111 tests) (#37) * Add Vitest test suite for frontend - 111 tests across utils, components, hooks, and graph utilities Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/7cf0dba2-ecff-4740-ba4d-92717e74a0b7 * ci: add frontend test step to CI workflow Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/5bc0ac9f-0a32-4d03-9cb7-7a15aea53fca --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * chore: simplify array initialization in test files for consistency * ran typecheck * feat: add AnalysisWorkspace component and integrate it into CfgViewerPage * feat: update routing in AppLayout and improve empty state message in ExplorerPage * feat: enhance scan progress tracking with additional metrics and stages * feat: update license information and add license check script * feat: implement cross-file symbolic execution with callee body persistence * feat: replace dagre graphs with Graphology + ELK + Sigma for more advanced call stack and cfg rendering * feat: ensure CFG function view is scoped to the selected function, preventing bleed into sibling functions * feat: enhance resource tracking with proxy method summaries and improve finding extraction * feat: add terminal function exit detection for accurate resource leak analysis * feat: add warnings for loops and functions without bodies to improve error recovery * feat: update lambda expression handling to ensure proper function classification and control flow * feat: remove bounded formatting/string ops and add JSON.parse sanitizer for improved data handling * feat: add inline return taint analysis and regression tests for improved security checks * feat: add engine version management and migration handling for database schema updates * feat: enhance first_call_ident to skip nested function bodies and add regression tests * feat: enhance callee name resolution with two-segment normalization and disambiguation * feat: add cross-file context flags and debug assertions for taint analysis * feat: refactor taint analysis structure to unify context handling and improve clarity * feat: enhance dead code elimination to preserve Sink, Source, and Sanitizer labels with new tests * docs: updated CHANGELOG.md * fmt: formatting fixes * fix: fixed frontend formatting and lint warnings * fix: optimized ci * fix: optimized ci * Add comprehensive multi-file test coverage to Nyx (#38) * Initial checklist for multi-file test suite expansion Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/e550cb88-9767-4442-94d4-101bf5bb0e23 Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * Add 12 new multi-file test fixtures with TP/TN/near-miss coverage Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/e550cb88-9767-4442-94d4-101bf5bb0e23 Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * deleted root repo * rebuilt to test for regressions --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Co-authored-by: elipeter <elicpeter@gmail.com> * feat: enhance import alias resolution and taint tracking * feat: implement security hardening with CSRF protection and path validation * feat: add support for import alias bindings in Python, PHP, and Rust * feat: enhance CFG analysis modes and improve code readability * feat: add detection for parameterized SQL queries to enhance security * feat: add safe internal redirect handling and enhance session destroy validation * feat: implement security improvements by addressing vulnerabilities in execAsync, session management, and file downloads * feat: enhance taint detection by adding support for inline source member expressions in call arguments * feat: implement pre-emission of Source nodes for inline source member expressions in call arguments * feat: add support for Throw statement in control flow and error handling * feat: add debug and echo endpoints with potential information leakage * feat: implement internal redirect suppression and enhance taint detection * feat: implement module alias tracking for dynamic dispatch in JS/TS * feat: add authorization analysis module with Express support * feat: add authorization analysis module with Express support * feat: add tests for admin guard requirements and clean checks in authorization analysis * feat: integrate Koa and Fastify frameworks into authorization analysis * feat: add Flask and Django support to authorization analysis module * feat: add support for Rails and Sinatra frameworks in authorization analysis * feat: add support for Axum, ActixWeb, and Rocket frameworks in authorization analysis * feat: add support for ActixWeb, Axum, and Rocket frameworks in authorization analysis * feat: add support for Rails and Sinatra in authorization analysis * chore: add .DS_Store to .gitignore * refactor: simplify conditional checks and improve readability in multiple files * refactor: update usage of Option methods for improved clarity and consistency * refactor: improve code readability by simplifying conditional checks and formatting * refactor: improve code formatting and readability by simplifying conditional checks * refactor: simplify conditional checks and improve readability in multiple files * refactor: simplify conditional checks in axum.rs for improved readability * feat: add CodeQL analysis configuration for enhanced security scanning * test: add comprehensive tests for `src/output.rs` SARIF builder (#39) * chore: start test coverage improvement work Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/cd7ff398-134e-4728-a5e7-0353a0744423 Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * test: add comprehensive tests for src/output.rs SARIF builder Agent-Logs-Url: https://github.com/elicpeter/nyx/sessions/cd7ff398-134e-4728-a5e7-0353a0744423 Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> * refactor: improve code formatting and readability in output.rs --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: elicpeter <54954007+elicpeter@users.noreply.github.com> Co-authored-by: elipeter <elicpeter@gmail.com> * refactor: improve code formatting and readability in output.rs * Potential fix for code scanning alert no. 210: Uncontrolled data used in path expression Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * Potential fix for code scanning alert no. 211: Uncontrolled data used in path expression Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> * refactor: enhance triage file path handling with improved error management and validation * refactor: updated func summaries for richer detail * refactor: update SSA summary extraction to use canonical FuncKey for distinct entries * refactor: enhance callee metadata structure to support arity, receiver, and qualifier for better overload resolution * refactor: add support for keyword arguments in function calls and enhance receiver extraction for method-style calls * refactor: implement new Flask routes for safe and unsafe shell command execution * refactor: separate receiver handling in SSA operations and enhance taint propagation * refactor: improve arity handling by using arg_uses for positional argument count and enhance witness scoring for tainted arguments * refactor: implement auth decorator extraction and classification for multiple languages * refactor: enhance Rust module path resolution and use map handling for cross-file disambiguation * refactor: introduce CalleeQuery struct for structured callee resolution and enhance resolver logic * refactor: implement same-file identity collision handling for `runTask` to ensure correct resolver behavior * refactor: standardize default struct initialization across multiple files * feat: add scripts for formatting checks and auto-fixes with test summaries * refactor: simplify character splitting and enhance namespace qualifier handling * refactor: improve documentation clarity and enhance code readability in resolver logic * refactor: replace default struct initialization with explicit field assignments for clarity * feat: enhance anonymous function naming by deriving context-based bindings * refactor: streamline match expressions for improved readability and performance * refactor: streamline match expressions for improved readability and performance * refactor: replace loop with while let for improved clarity and performance * feat: add SSA constant propagation support to analysis context for improved accuracy * feat: add SSA constant propagation support to analysis context for improved accuracy * feat: implement shell metacharacter validation and bounded-length checks in Rust analysis * feat: add static map analysis for command injection suppression and type safety * refactor: simplify match statements and reduce line breaks for improved readability * feat(summary): phase 1/5 SinkSite data model for primary sink-location attribution Introduce SinkSite (file_rel, line, col, snippet, cap) carrying the primary sink source-location through function summaries. Swap SsaFuncSummary.param_to_sink and FuncSummary.param_to_sink from a coarse Cap map to a deduped SmallVec<[SinkSite; 1]> per parameter, with a backward-compatible cap_sites() helper and serde defaults so pre-phase-1 on-disk rows continue to deserialise cleanly. Extraction: SinkSiteLocator bundles the tree/bytes/file_rel needed by extract_ssa_func_summary; ParsedFile::extract_ssa_artifacts wires the locator in for the persisted pass-1 path, while pass-2 intra-file transient summaries fall back to cap-only sites (behavior unchanged). Merge: GlobalSummaries::insert now unions sink sites with (file_rel, line, col, cap) dedup via shared union_param_sink_sites helper. Database: JSON-serialised summary columns carry the new shape automatically; no schema change needed. Phase 2 will consume SinkSite in build_taint_diag() to overwrite the caller-site Finding.line with the callee's sink line when resolved via summary. Phase 1 keeps behavior unchanged: scanning tests/benchmark/corpus/rust/cmdi/cmdi_indirect.rs still produces the same (wrong) line 10 finding. Adds round-trip tests covering SinkSite solo, SsaFuncSummary with sink sites, legacy-JSON default handling for both summary types, and merge dedup. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * feat(taint): phase 2/5 thread SinkSite into SsaTaintEvent and Finding Plumb Phase 1's SinkSite through the event pipeline into Findings, no output change yet. SsaTaintEvent gains `primary_sink_site: Option<SinkSite>`; when the main or callback sink-emission path has non-empty `param_to_sink_sites`, filter to sites whose `(line != 0) && (cap ∩ sink_caps != ∅)` and emit one event per distinct site — the multi-primary collapse keeps each downstream Finding single-primary. Resolution: ResolvedSummary and SinkInfo gain mirror `param_to_sink_sites` fields, populated from `SsaFuncSummary.param_to_sink` (SSA + callback paths) and `FuncSummary.param_to_sink` (global paths). Label, local-summary, and interop resolution paths leave the field empty — they only ever had cap-level info to begin with. Finding: new `primary_location: Option<SinkLocation>` with `file_rel/line/col`. `ssa_events_to_findings` maps `event.primary_sink_site` → `Finding.primary_location`, filtering cap-only sites (`line == 0`) to `None` so the (0,0) sentinel never leaks to formatters. Dedup key extended with the primary location so multi-site events aren't collapsed back together. Invariants (debug_assert!): * every SinkSite reaching emission has `line != 0 && cap ∩ sink_caps != ∅` — enforced by the pick_primary_sink_sites* filters; * every populated Finding.primary_location has `line != 0` AND non-empty `file_rel` — the cap-only → None translation upstream guarantees this. Deliberately independent of `uses_summary`: that flag tracks whether the *taint chain* used a summary, whereas primary attribution requires only that the *sink* itself was summary-resolved. A local source reaching a cross-file sink produces `uses_summary=false` alongside a populated primary_location — documented on Finding.primary_location, covered by `cross_file_sink_finding_carries_primary_location`. build_taint_diag, SARIF/JSON/explanation formatters, and the benchmark scorer remain untouched: finding.line still comes from `cfg_graph[finding.sink]`, so cmdi_indirect.rs still reports line 10 and the benchmark's rs-cmdi-003 row still shows FN in the LOC column. Tests: `cross_file_sink_finding_carries_primary_location` (proves plumbing via a synthetic FuncSummary carrying a SinkSite at 42:5) and `cross_file_sink_cap_only_site_leaves_primary_location_none` (regression guard against cap-only sites surfacing). All 1566 lib tests + integration tests pass. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(output): phase 3/5 consume primary sink location in diag + SARIF When a finding's primary_location (populated in phase 2 from a callee summary's SinkSite) names the dangerous instruction inside a callee body, attribute the diagnostic line to that location instead of the caller's call site. The call site is demoted to a Call step in flow_steps, and a synthetic Sink step at the primary location is appended so analysts still see the full trace. Changes: - Add scan_root parameter to build_taint_diag so file_rel can be resolved back to an absolute path via a shared resolve_file_rel helper. Empty file_rel (single-file scans where namespace == "") resolves to the file under analysis. - Extend SinkLocation with snippet, carried from the upstream SinkSite so the formatter needs no second file read. - Relax the ssa_events_to_findings debug_assert to allow empty file_rel, which is valid when scan root equals the file itself. - SARIF: emit data-flow as codeFlows[0].threadFlows[0].locations[]; locations[0] already reflects the primary sink position via the updated diag line/col. Acceptance: scan on tests/benchmark/corpus/rust/cmdi/cmdi_indirect.rs now reports line 5 (Command::new) as the primary sink, with the call site at line 10 visible in flow_steps. Two expect.json fixtures updated (must_match line_range widened): - javascript/taint/context_sensitive_call: 12-14 -> 7-14 (line 8 is the real sink inside run()). - rust/cfg/closure_async: 10-10 -> 10-11 (line 11 is Command::new inside the closure). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(bench): phase 4/5 validate primary sink attribution across corpus Extend the benchmark scorer and ground truth to lock in phase 3's primary-location behavior, and add fixtures that exercise the new capability end-to-end. Scorer (tests/benchmark_test.rs): - Add optional `expected_call_site_lines: Option<Vec<[usize; 2]>>` on Case. When present, score_location_level additionally requires at least one flow_step in the finding's evidence trace to fall within ±2 of the call-site range. When absent, the check is skipped — fully forward-compatible with existing fixtures. - Retain ±2 tolerance on expected_sink_lines (compared against the now-primary Diag.line post-phase-3). Ground truth edits: - rs-cmdi-cross-001: expected_sink_lines [8,8] -> [9,9]. Line 8 is the transform::wrap call site (a cross-file propagator, not a sink); line 9 is Command::new, the real sink. The ±2 tolerance happened to mask this stale attribution but it was semantically wrong — phase 4 is the right time to correct it. Also adds expected_call_site_lines [8,8] so the new field is exercised on an existing cross-file case. - rs-cmdi-003: adds expected_call_site_lines [10,10] (run_cmd call). This fixture's sink (Command::new inside run_cmd at line 5) was the motivating case for phases 1-3; adding the call-site assertion guards against regression to caller-line attribution. New fixtures: - rust/cmdi/cmdi_indirect_multisink.rs (rs-cmdi-009): helper run_both takes two tainted params and invokes two Command sinks on consecutive lines. Locks in that primary line lands inside the helper (lines 5-6), not at the caller (line 12). Notes document that SinkSite is currently one-per-callee so both findings today collapse onto the first sink; expected_sink_lines=[5,6] and expected_call_site_lines=[12,12] stay valid either way. - python/cmdi/cross_indirect_sink/{app.py,helper.py} (py-cmdi-cross- 004): sink os.system lives in helper.py (cross-file), caller in app.py reads env source and calls run_cmd. Verifies phase 3's cross-file primary attribution: Diag.path = helper.py, Diag.line = 5, with app.py:7 recorded in flow_steps as a Call step. Acceptance: - `cargo test --test benchmark_test -- --ignored --nocapture` passes. - rs-cmdi-003 is TP/TP/TP (the target flip FN->TP at LOC). All pre-existing TP/TP/TP fixtures remain TP/TP/TP; 2 new fixtures are TP/TP/TP. - Aggregate rule-level: TP=158 FP=10 FN=1 TN=97, P=0.940 R=0.994 F1=0.966 on the 266-case corpus (was TP=156 FP=10 FN=1 TN=97 on 264 pre-phase-4, delta is the +2 new cases both resolving TP). - Full `cargo test` green (1566 lib tests + all integration tests). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(taint): phase 5/5 lock Finding.primary_location contract via regression test Add a regression test in src/taint/ssa_transfer.rs that wires up a synthetic SsaFuncSummary with a SinkSite at other.rs:42:10 and drives the three emission stages (pick_primary_sink_sites → emit_ssa_taint_events → ssa_events_to_findings) against a minimal caller SSA body. Asserts the resulting Finding.primary_location is exactly that triple. The existing integration tests in src/taint/tests.rs cover the coarse FuncSummary path end-to-end through analyse_file. This test locks in the lower-level SSA-side plumbing so a future refactor that silently drops the site between pick → emit → findings fails here rather than only at the benchmark layer. Also refreshes tests/benchmark/results/latest.json (timestamp only; rs-cmdi-003 remains TP/TP/TP and the aggregate P/R/F1 are unchanged from phase 4). Closes the primary sink-location attribution feature (phases 1-5/5): * Phase 1 — SinkSite data model on summaries. * Phase 2 — SinkSite threaded into SsaTaintEvent and Finding. * Phase 3 — diag + SARIF consume primary_location. * Phase 4 — benchmark validates primary_call_site_lines across corpus. * Phase 5 — regression test locks the event→finding contract. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * refactor: clean up formatting and improve readability in multiple files * refactor: simplify type definition for deduplication key in findings * test(harness): add must_not_match expectation for FP regression guards Extends ExpectedFinding with must_not_match field that asserts a diagnostic must NOT fire — presence is a hard failure. Non-consuming scan so it coexists with must_match entries on the same rule_id. Adds forbidden_violations accumulator and updates summary line. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat(regression): update expectations to ensure must_not_match for various taint and resource leak rules * feat: implement auto-seeding for JS/TS handler parameters to enhance taint tracking * feat: update switch statement handling to improve control flow analysis * feat: implement promisify alias handling for JS/TS to enhance taint tracking * feat: enhance taint tracking by refining expectation handling and adding mode filtering * feat: refine SQL handling in stream processing and enhance auto-seeding for handler parameters * feat: update taint tracking rules to enforce full mode matching and improve flow analysis * feat: enhance Ruby subshell handling to improve taint tracking and flow analysis * feat: update xss_response expectations to refine taint flow analysis and enhance regression guarding * feat: refine framework detection and update expectation handling for Echo and Sinatra * feat: implement max_count for taint tracking expectations and deduplicate findings * feat: add strict_unexpected handling for taint-unsanitised-flow in expectation files * feat: enhance deduplication of taint-unsanitised-flow findings by collapsing based on line and severity * feat: add strict_unexpected handling for taint-unsanitised-flow in multiple expectation files * feat: add structural invariant checks for SSA bodies * feat: ensure deterministic phi emission order using BTreeSet * feat: enhance handling of terminators to ensure authoritative flow through successor edges * feat: enhance Goto terminator handling to ensure all successors are marked executable * feat: refactor code for improved readability and organization * feat: simplify predicate checks and enhance readability in SSA handling * feat: implement per-file parse timeout and enhance file size handling * feat: migrate analysis engine toggles from environment variables to configuration file * feat: remove unnecessary whitespace in hostile_input_tests.rs * feat: remove unnecessary whitespace in hostile_input_tests.rs * feat: update dependencies and enhance documentation on language maturity * feat: enhance security headers and improve request body limits * feat: implement sink capability bits for deduplication and enhance evidence tagging * feat: implement dynamic activation handling for gated sinks and enhance validation logic * feat: enhance configuration documentation and clarify inline analysis cache behavior * feat: implement panic recovery during analysis to continue scans past errors * feat: add expectations configuration for taint analysis and performance metrics * feat: enhance error handling and logging during file reading and mutex locking * feat: add cross-file body loading tests and plumbing for CF-1 phase * feat: implement cross-file k=1 context-sensitive inline taint analysis with new tests and fixtures * feat: implement indexed-scan parity in cross-file inline analysis with new dropdown and copy functionality * feat: enhance classification span handling in CFG and AST for improved source attribution * feat: add new Express routes for handling user input and telemetry data * feat: implement ternary expression handling in CFG with diamond structure for JS/TS * feat: implement Phase CF-3 abstract-domain transfer channels in summaries * feat: add support for string-prefix transfer in cross-file calls and update tests * docs: reduce RESULTS.md doc size * feat: implement Phase CF-4 per-return-path summary decomposition with tests * feat: update parameter handling in pass1 and refactor SsaFuncSummary initialization * feat: implement Phase CF-5 for cross-file SCC joint fixed-point convergence with new flags and tests * feat: implement Phase CF-6 with parameter-granularity points-to summaries and associated tests * refactor: update comments and documentation for clarity and consistency * style: format code for consistency and readability * refactor: simplify verdict handling and improve edge checking logic * refactor: optimize path and identifier collection by avoiding unnecessary cloning * chore: update Cargo.toml for Rust version 1.85 and add ignored files; modify CHANGELOG and README for clarity on state analysis defaults * refactor: update documentation and improve clarity in configuration files * refactor: update documentation and improve clarity in configuration files * feat: add JS/TS pass-2 convergence tests and expectations configuration * feat: add Phase 5 regression tests for inline cache origin attribution and update related logic * feat: implement Phase 7 deduplication and alternative path linking for taint findings * feat: implement structural DFS index for anonymous functions and update naming conventions * feat: add Phase 8 regression tests for container-element taint in JS and Python * feat: add engine-depth profiles and explain-engine option for CLI * feat: update expectations and add new README fixtures for multi-file scan regression * feat: implement Phase 11 callback-alias and factory patterns with regression tests * feat: implement Terminator::Switch for multi-way dispatch and add regression tests * feat: add real-CVE benchmark fixtures for CVE-2023-48022, CVE-2019-14939, and CVE-2023-26159 with corresponding patched variants * refactor: extract cfg and ssa_transfer to submodules * refactor: cargo fmt * refactor: remove unnecessary blank line in cfg_tests.rs * refactor: remove unnecessary planning file * chore: update Rust version to 1.88 and bump dependencies in Cargo files * feat: enhance triage UI with new layout and controls, update README for clarity * feat: enhance triage UI with new layout and controls, update README for clarity * chore: remove outdated section from README for version 0.5.0 * docs: improve clarity and consistency in README content * chore: add "GPL-3.0-or-later" to license options in about.toml * chore: update license handling in about.toml and check-licenses.mjs * style: format code for improved readability in TriagePage component * style: format code for improved readability in TriagePage component * chore: enhance license handling and improve body_id scoping in seed lookup * feat: introduce owner and parent body IDs for enhanced seed scoping * feat: implement direction-aware engine provenance with new CLI flag for strict CI gating * feat: add Undef SSA operation for improved control-flow handling * style: improve code formatting for consistency and readability in multiple files * feat: add 16-function chain SCC across multiple files for enhanced analysis * style: simplify code formatting for improved readability in multiple files * fix: update CapHitReason default implementation and improve README clarity * docs: enhance README with detailed explanations of taint analysis and limitations * docs: refine README for clarity and consistency in taint analysis section * style: improve code formatting for better readability in NewScanModal and scans * fix: update cargo-about command to use --offline for deterministic license generation * fix: update cargo-about command to use --offline for deterministic license generation * ci: add step to prime cargo registry cache for deterministic license generation * feat: add support for non-sink collections in authorization analysis * feat: enhance authorization checks with row-level ownership equality and binding tracking * feat: implement self-scoped user handling and enhance ownership checks * refactor: simplify assertions and formatting in authorization analysis tests * fix: normalize line endings in THIRDPARTY-LICENSES.html generation and update README with AI disclosure * docs: update AI disclosure section for clarity and conciseness * feat: add AI Contribution Policy and update contributing guidelines for AI assistance disclosure * feat: enhance authorization analysis with SSA-derived variable type classification * feat: implement auth_finding_to_diag function for enhanced security diagnostics * feat: add args_value_refs to CallSite struct for enhanced argument tracking * feat: add args_value_refs to CallSite struct for enhanced argument tracking * feat: add direction-aware engine provenance with LossDirection classification and new CLI flag * feat: simplify strip_cap_from_call_args call by removing unnecessary line breaks * feat: enhance error message handling in cli_validation_tests for better Windows compatibility * feat: optimize release profile settings in Cargo.toml and update CodeQL configuration * feat: enhance release build process with SBOM generation and SLSA provenance * feat: update actions/checkout and actions/setup-node to v6, enhance CLI options, and improve auth-check summaries * feat: introduce PathFact handling for path safety checks and rejection logic * feat: introduce PathFact handling for path safety checks and rejection logic * feat: update benchmark data and enhance path sanitization logic with new safety checks * feat: document AI assistance in frontend UI development and human review process * feat: add return path facts for enhanced path safety checks and update documentation * chore: update release date for version 0.5.0 in CHANGELOG.md * chore: clean up ci.yml by removing outdated comments and clarifying steps * feat: implement cross-language path sanitizers and validators for enhanced security * feat: enhance SSA value usage tracking by including block terminators and improve path safety checks * feat: enhance switch statement handling by adding per-case path constraints and support for exclusive cases * refactor: simplify conditional formatting and improve code readability in executor and lower modules * feat: add vulnerable examples for various languages demonstrating authentication and sanitization issues * feat: enhance actor context recognition for self-actor identifiers and add support for global non-sink receivers * feat: enhance actor context recognition for self-actor identifiers and add support for global non-sink receivers * feat: add transform classifiers for Java, Go, and Ruby with corresponding tests * refactor: clarify comments on reassign-to-constant idiom and sink behavior in guards.rs --------- Co-authored-by: Copilot <198982749+Copilot@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
530 lines
22 KiB
Rust
530 lines
22 KiB
Rust
//! Hostile-input / resource-exhaustion regression tests.
|
|
//!
|
|
//! Nyx scans untrusted repositories, so every file the scanner picks up is
|
|
//! potentially adversarial: arbitrarily large, pathologically nested,
|
|
//! binary-ish, or deliberately crafted to wedge tree-sitter or the CFG
|
|
//! builder. These tests exercise the user-facing size cap
|
|
//! (`scanner.max_file_size_mb`, default 16 MiB — enforced at the walker),
|
|
//! the per-file parse timeout (`analysis.engine.parse_timeout_ms`, default
|
|
//! 10 s), and
|
|
//! verify that the scanner survives several representative stress inputs
|
|
//! without panicking, stack-overflowing, or hanging CI.
|
|
//!
|
|
//! All tests stay well under the 10 s taint-termination guard used elsewhere
|
|
//! so they are safe for the default test job. Keep file sizes modest so
|
|
//! CI runners with limited RAM/disk are not penalised.
|
|
|
|
use nyx_scanner::ast::run_rules_on_bytes;
|
|
use nyx_scanner::utils::config::{AnalysisMode, Config};
|
|
use std::path::Path;
|
|
use std::thread;
|
|
use std::time::{Duration, Instant};
|
|
|
|
/// Match the production rayon worker stack size (`performance.rayon_thread_stack_size`).
|
|
/// Tests that exercise recursive CFG construction must run here, not on the
|
|
/// default 2 MiB test thread, so they represent the real scan environment.
|
|
const PROD_STACK_SIZE: usize = 8 * 1024 * 1024;
|
|
|
|
/// Run `f` on a dedicated thread with a production-sized stack. Panics in
|
|
/// `f` are propagated so the test fails with the original message.
|
|
fn run_on_prod_stack<F, R>(f: F) -> R
|
|
where
|
|
F: FnOnce() -> R + Send + 'static,
|
|
R: Send + 'static,
|
|
{
|
|
thread::Builder::new()
|
|
.stack_size(PROD_STACK_SIZE)
|
|
.name("hostile-input-prod-stack".into())
|
|
.spawn(f)
|
|
.expect("spawn test thread")
|
|
.join()
|
|
.expect("test thread panicked")
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// Helpers
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// Minimal config tuned for deterministic, single-threaded scans in CI.
|
|
fn hostile_cfg() -> Config {
|
|
let mut cfg = Config::default();
|
|
cfg.scanner.mode = AnalysisMode::Full;
|
|
cfg.scanner.read_vcsignore = false;
|
|
cfg.scanner.require_git_to_read_vcsignore = false;
|
|
cfg.performance.worker_threads = Some(1);
|
|
cfg.performance.batch_size = 8;
|
|
cfg.performance.channel_multiplier = 1;
|
|
cfg
|
|
}
|
|
|
|
/// Run a closure and fail the test if it does not complete within `budget`.
|
|
/// Used to keep these regression tests from silently turning into CI hangs
|
|
/// if a bound regresses.
|
|
fn with_time_budget<F, R>(budget: Duration, label: &str, f: F) -> R
|
|
where
|
|
F: FnOnce() -> R,
|
|
{
|
|
let start = Instant::now();
|
|
let out = f();
|
|
let elapsed = start.elapsed();
|
|
assert!(
|
|
elapsed < budget,
|
|
"{label} took {elapsed:?}, exceeded budget {budget:?}",
|
|
);
|
|
out
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// File-size hardening (walker-level)
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// The walker's `max_file_size_mb` filter must drop oversize files before
|
|
/// the pipeline ever opens them. This is the sole file-size gate: once a
|
|
/// file is past the walker, the analysis pipeline does not re-check its
|
|
/// size — `max_file_size_mb = null` means truly unlimited parsing. The
|
|
/// pattern here (explicit `Some(1)`) is the interface every downstream
|
|
/// caller can use to tighten the default further.
|
|
#[test]
|
|
fn walker_max_file_size_drops_oversize_files_before_scan() {
|
|
use nyx_scanner::scan_no_index;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
std::fs::write(root.join("small.js"), b"var x = 1;\n").unwrap();
|
|
let big = vec![b'x'; 3 * 1024 * 1024];
|
|
std::fs::write(root.join("big.js"), big).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.max_file_size_mb = Some(1); // 1 MiB — drops big.js, keeps small.js
|
|
|
|
let diags =
|
|
scan_no_index(root, &cfg).expect("scan should succeed even with oversize files present");
|
|
assert!(
|
|
diags.iter().all(|d| !d.path.ends_with("big.js")),
|
|
"big.js should have been filtered by walker, got: {diags:?}",
|
|
);
|
|
}
|
|
|
|
/// Release-hardening regression: the default `ScannerConfig` must carry a
|
|
/// finite ceiling so a fresh install never tries to parse a multi-gigabyte
|
|
/// file from an untrusted repo. This test does not hard-code the exact
|
|
/// value — the property is that the default is *not* unlimited.
|
|
#[test]
|
|
fn default_config_has_finite_max_file_size() {
|
|
let cfg = Config::default();
|
|
assert!(
|
|
cfg.scanner.max_file_size_mb.is_some(),
|
|
"release default must not be unlimited; got {:?}",
|
|
cfg.scanner.max_file_size_mb,
|
|
);
|
|
let limit = cfg.scanner.max_file_size_mb.unwrap();
|
|
assert!(
|
|
(1..=64).contains(&limit),
|
|
"default file-size cap should live in [1, 64] MiB, got {limit} MiB",
|
|
);
|
|
}
|
|
|
|
/// A file above the default cap must be dropped by the walker when the
|
|
/// config is left at its defaults. End-to-end version of the property
|
|
/// asserted above.
|
|
#[test]
|
|
fn default_config_drops_file_above_cap() {
|
|
use nyx_scanner::scan_no_index;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
std::fs::write(root.join("small.js"), b"var x = 1;\n").unwrap();
|
|
|
|
// Write a file larger than the default cap. Size = default + 1 MiB so
|
|
// the test does not spuriously fail if the default is adjusted later.
|
|
let default_mb = Config::default()
|
|
.scanner
|
|
.max_file_size_mb
|
|
.expect("default cap must be set");
|
|
let oversize = ((default_mb + 1) as usize) * 1024 * 1024;
|
|
let mut big = b"// big generated file\n".to_vec();
|
|
big.resize(oversize, b' ');
|
|
std::fs::write(root.join("big.js"), &big).unwrap();
|
|
|
|
// Use the release default cap explicitly so the intent is clear.
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.max_file_size_mb = Config::default().scanner.max_file_size_mb;
|
|
|
|
let diags = with_time_budget(Duration::from_secs(10), "default-cap scan", || {
|
|
scan_no_index(root, &cfg).expect("scan must succeed with oversize file present")
|
|
});
|
|
assert!(
|
|
diags.iter().all(|d| !d.path.ends_with("big.js")),
|
|
"default cap should have filtered big.js: got {diags:?}",
|
|
);
|
|
}
|
|
|
|
/// Operators who explicitly set `max_file_size_mb = null` must actually get
|
|
/// unlimited scanning — no silent hard cap overrides their decision. This
|
|
/// locks in the contract: "unlimited means unlimited, trust the operator."
|
|
/// The test uses a deliberately unsafe-looking JS source and asserts that
|
|
/// the finding surfaces only in the unlimited run.
|
|
#[test]
|
|
fn explicit_unlimited_lifts_size_cap() {
|
|
use nyx_scanner::scan_no_index;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
// Build a 2 MiB file with a detectable vulnerability at the top.
|
|
// tight_cap (1 MiB) must hide it; unlimited must surface it.
|
|
let mut bytes = b"const cp = require('child_process');\n\
|
|
function run(cmd){ cp.exec(cmd); }\n"
|
|
.to_vec();
|
|
bytes.resize(2 * 1024 * 1024, b'\n');
|
|
std::fs::write(root.join("big.js"), &bytes).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
|
|
// 1 MiB cap — must drop big.js entirely.
|
|
cfg.scanner.max_file_size_mb = Some(1);
|
|
let tight = scan_no_index(root, &cfg).expect("tight-cap scan must succeed");
|
|
assert!(
|
|
tight.iter().all(|d| !d.path.ends_with("big.js")),
|
|
"sanity: tight cap must have dropped big.js: {tight:?}",
|
|
);
|
|
|
|
// Explicit unlimited — the same file must now be visible to the
|
|
// scanner. Any pipeline exception would surface as a non-success.
|
|
cfg.scanner.max_file_size_mb = None;
|
|
let unlimited = with_time_budget(Duration::from_secs(20), "unlimited scan", || {
|
|
scan_no_index(root, &cfg).expect("explicit-unlimited scan must succeed")
|
|
});
|
|
assert!(
|
|
unlimited.iter().any(|d| d.path.ends_with("big.js")),
|
|
"explicit unlimited must scan big.js; got {unlimited:?}",
|
|
);
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// Binary / junk / encoding hardening
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// Random binary noise (NUL-heavy) must be detected and skipped quickly.
|
|
#[test]
|
|
fn binary_null_heavy_input_is_skipped() {
|
|
// 256 KiB with every third byte NUL → well above the 1% NUL threshold.
|
|
let mut bytes = vec![0xCCu8; 256 * 1024];
|
|
for i in (0..bytes.len()).step_by(3) {
|
|
bytes[i] = 0;
|
|
}
|
|
|
|
let path = Path::new("junk.c");
|
|
let cfg = hostile_cfg();
|
|
let diags = with_time_budget(Duration::from_secs(2), "binary skip", || {
|
|
run_rules_on_bytes(&bytes, path, &cfg, None, None).expect("binary file should not error")
|
|
});
|
|
assert!(
|
|
diags.is_empty(),
|
|
"binary-looking files must be skipped, got {} diags",
|
|
diags.len()
|
|
);
|
|
}
|
|
|
|
/// Invalid UTF-8 in a recognised source extension must not panic.
|
|
/// tree-sitter can operate on raw bytes; we just check that it survives.
|
|
#[test]
|
|
fn invalid_utf8_does_not_panic() {
|
|
let bytes = b"\xff\xfe\xfd\xfc\n\xde\xad\xbe\xef\n// trailing\n".to_vec();
|
|
let path = Path::new("junk.rs");
|
|
let cfg = hostile_cfg();
|
|
let _ = with_time_budget(Duration::from_secs(2), "invalid utf8", || {
|
|
run_rules_on_bytes(&bytes, path, &cfg, None, None).expect("invalid UTF-8 should not error")
|
|
});
|
|
}
|
|
|
|
/// An empty file must produce no findings and no errors. Trivial, but it
|
|
/// was a historical source of div-by-zero bugs in `is_binary`.
|
|
#[test]
|
|
fn empty_file_is_noop() {
|
|
let path = Path::new("empty.js");
|
|
let cfg = hostile_cfg();
|
|
let diags = run_rules_on_bytes(b"", path, &cfg, None, None).expect("empty file should be ok");
|
|
assert!(diags.is_empty());
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// Structural stress: long lines and deep nesting
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// A source file consisting of a single extremely long line must parse
|
|
/// without blowing up. Minified bundles routinely hit this shape. We
|
|
/// model it as ~10 000 independent short statements on one line (roughly
|
|
/// what you see after bundler output) rather than one 500k-deep
|
|
/// right-associative expression — the latter is a separate stress case
|
|
/// dominated by recursive descent and not representative of real input.
|
|
///
|
|
/// Generous debug-build budget (20 s) because the full analysis pipeline
|
|
/// runs on every statement; release builds are an order of magnitude
|
|
/// faster. The point is to guard against regressions that are
|
|
/// super-linear in statement count, not to benchmark.
|
|
#[test]
|
|
fn very_long_single_line_parses() {
|
|
run_on_prod_stack(|| {
|
|
let mut s = String::with_capacity(128 * 1024);
|
|
for i in 0..10_000 {
|
|
s.push_str(&format!("var a{i}=1;"));
|
|
}
|
|
s.push('\n');
|
|
|
|
let path = Path::new("long_line.js");
|
|
let cfg = hostile_cfg();
|
|
let _ = with_time_budget(Duration::from_secs(20), "long line parse", || {
|
|
run_rules_on_bytes(s.as_bytes(), path, &cfg, None, None)
|
|
.expect("long-line file should parse")
|
|
});
|
|
});
|
|
}
|
|
|
|
/// Deeply-nested parentheses exercise the recursive descent in tree-sitter
|
|
/// and the recursive `build_sub` in `cfg::build_cfg`. Runs on a thread
|
|
/// sized to match the production rayon stack so the test environment
|
|
/// matches the real scan environment. 500 levels leaves comfortable
|
|
/// headroom; a regression that doubled the per-frame cost would trip this.
|
|
#[test]
|
|
fn deeply_nested_parens_do_not_stack_overflow() {
|
|
run_on_prod_stack(|| {
|
|
const DEPTH: usize = 500;
|
|
let mut s = String::with_capacity(DEPTH * 4);
|
|
s.push_str("var x = ");
|
|
for _ in 0..DEPTH {
|
|
s.push('(');
|
|
}
|
|
s.push('1');
|
|
for _ in 0..DEPTH {
|
|
s.push(')');
|
|
}
|
|
s.push_str(";\n");
|
|
|
|
let path = Path::new("deep_parens.js");
|
|
let cfg = hostile_cfg();
|
|
let _ = with_time_budget(Duration::from_secs(10), "deep parens parse", || {
|
|
run_rules_on_bytes(s.as_bytes(), path, &cfg, None, None)
|
|
.expect("deeply nested parens should parse")
|
|
});
|
|
});
|
|
}
|
|
|
|
/// Deeply-nested `if` statements are the classical stress case for the CFG
|
|
/// builder. Each `if` frame in `build_sub` is ~10 KiB on debug builds, so
|
|
/// 100 levels fits comfortably inside the production 8 MiB stack with room
|
|
/// for the rest of the analysis pipeline above it. The goal is not to
|
|
/// probe the absolute limit — it is to lock in that a realistic generated-
|
|
/// code depth does not crash the scanner.
|
|
#[test]
|
|
fn deeply_nested_if_statements_do_not_stack_overflow() {
|
|
run_on_prod_stack(|| {
|
|
const DEPTH: usize = 100;
|
|
let mut s = String::with_capacity(DEPTH * 16);
|
|
s.push_str("function f(x){\n");
|
|
for i in 0..DEPTH {
|
|
for _ in 0..i {
|
|
s.push(' ');
|
|
}
|
|
s.push_str("if (x) {\n");
|
|
}
|
|
for i in (0..DEPTH).rev() {
|
|
for _ in 0..i {
|
|
s.push(' ');
|
|
}
|
|
s.push_str("}\n");
|
|
}
|
|
s.push_str("}\n");
|
|
|
|
let path = Path::new("deep_if.js");
|
|
let cfg = hostile_cfg();
|
|
let _ = with_time_budget(Duration::from_secs(10), "deep if parse", || {
|
|
run_rules_on_bytes(s.as_bytes(), path, &cfg, None, None)
|
|
.expect("deeply nested ifs should parse")
|
|
});
|
|
});
|
|
}
|
|
|
|
/// Lots of small functions in one file stresses the pass-1/pass-2 bookkeeping
|
|
/// (summary extraction, callgraph build). 2 000 functions is cheap but
|
|
/// plausible for generated code.
|
|
#[test]
|
|
fn many_small_functions_do_not_explode() {
|
|
let mut s = String::with_capacity(2000 * 32);
|
|
for i in 0..2000 {
|
|
s.push_str(&format!("function f{i}(x) {{ return x + {i}; }}\n"));
|
|
}
|
|
|
|
let path = Path::new("many_funcs.js");
|
|
let cfg = hostile_cfg();
|
|
let _ = with_time_budget(Duration::from_secs(15), "many-funcs scan", || {
|
|
run_rules_on_bytes(s.as_bytes(), path, &cfg, None, None)
|
|
.expect("many-functions file should scan")
|
|
});
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// End-to-end: hostile directory scan
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// A tempdir mixing several adversarial files must scan to completion in
|
|
/// bounded time and produce a well-formed diag list. This is the smoke
|
|
/// test most likely to catch a regression that composes badly across files.
|
|
#[test]
|
|
fn scan_of_mixed_hostile_directory_is_bounded() {
|
|
use nyx_scanner::scan_no_index;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
// Legitimate file so the scan has real work to do.
|
|
std::fs::write(
|
|
root.join("normal.js"),
|
|
b"const cp = require('child_process');\n\
|
|
function run(cmd) { cp.exec(cmd); }\n",
|
|
)
|
|
.unwrap();
|
|
|
|
// Binary noise.
|
|
let mut junk = vec![0xAAu8; 64 * 1024];
|
|
for i in (0..junk.len()).step_by(3) {
|
|
junk[i] = 0;
|
|
}
|
|
std::fs::write(root.join("junk.c"), junk).unwrap();
|
|
|
|
// Long single line.
|
|
let mut long = b"var y = ".to_vec();
|
|
long.extend(std::iter::repeat_n(b'a', 256 * 1024));
|
|
long.extend_from_slice(b";\n");
|
|
std::fs::write(root.join("long.js"), &long).unwrap();
|
|
|
|
// Deeply-nested parens.
|
|
let mut deep = String::from("var z = ");
|
|
for _ in 0..200 {
|
|
deep.push('(');
|
|
}
|
|
deep.push('1');
|
|
for _ in 0..200 {
|
|
deep.push(')');
|
|
}
|
|
deep.push_str(";\n");
|
|
std::fs::write(root.join("deep.js"), deep).unwrap();
|
|
|
|
// Oversize-for-walker (2 MiB; walker configured to drop it).
|
|
let big = vec![b'x'; 2 * 1024 * 1024];
|
|
std::fs::write(root.join("big.js"), big).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.max_file_size_mb = Some(1);
|
|
|
|
let diags = with_time_budget(Duration::from_secs(30), "hostile dir scan", || {
|
|
scan_no_index(root, &cfg).expect("scan must not fail on hostile inputs")
|
|
});
|
|
|
|
// The walker must drop big.js.
|
|
assert!(
|
|
diags.iter().all(|d| !d.path.ends_with("big.js")),
|
|
"walker should have filtered big.js"
|
|
);
|
|
// The legitimate file should still yield its cmdi finding.
|
|
assert!(
|
|
diags.iter().any(|d| d.path.ends_with("normal.js")),
|
|
"normal.js should still produce findings: {diags:?}",
|
|
);
|
|
}
|
|
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
// Symlink loops — infinite-loop resistance
|
|
// ───────────────────────────────────────────────────────────────────────────
|
|
|
|
/// A self-referencing symlink (`a/self -> ../a`) is a classic hostile-input
|
|
/// shape: a naive follow-symlinks walker will recurse forever. The `ignore`
|
|
/// crate's `WalkBuilder` handles cycles, but the scanner wraps that behind
|
|
/// its own canonicalization + containment check; a regression that re-enables
|
|
/// a cyclic walk would hang CI indefinitely. The test enforces a hard wall-
|
|
/// clock budget so a hang is caught as a timeout rather than as silent CI
|
|
/// stall.
|
|
#[cfg(unix)]
|
|
#[test]
|
|
fn symlink_loop_does_not_hang_with_follow() {
|
|
use nyx_scanner::scan_no_index;
|
|
use std::os::unix::fs::symlink;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
// Real file so the scan has legitimate work to do.
|
|
std::fs::write(root.join("real.js"), b"var x = 1;\n").unwrap();
|
|
|
|
// Nested directory with a self-referencing symlink: `a/self -> ../a`
|
|
// expands infinitely under a naive follow-symlinks walk.
|
|
let a = root.join("a");
|
|
std::fs::create_dir(&a).unwrap();
|
|
std::fs::write(a.join("inside.js"), b"var y = 2;\n").unwrap();
|
|
symlink("../a", a.join("self")).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.follow_symlinks = true;
|
|
|
|
let _diags = with_time_budget(Duration::from_secs(10), "symlink loop follow=true", || {
|
|
scan_no_index(root, &cfg).expect("scan of cyclic symlink tree must not error")
|
|
});
|
|
}
|
|
|
|
/// Same fixture with `follow_symlinks = false` must also terminate in
|
|
/// bounded time — the symlink is not followed, so the loop never expands,
|
|
/// but we pin the contract so flipping the default cannot introduce a hang
|
|
/// regression.
|
|
#[cfg(unix)]
|
|
#[test]
|
|
fn symlink_loop_does_not_hang_without_follow() {
|
|
use nyx_scanner::scan_no_index;
|
|
use std::os::unix::fs::symlink;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
std::fs::write(root.join("real.js"), b"var x = 1;\n").unwrap();
|
|
let a = root.join("a");
|
|
std::fs::create_dir(&a).unwrap();
|
|
std::fs::write(a.join("inside.js"), b"var y = 2;\n").unwrap();
|
|
symlink("../a", a.join("self")).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.follow_symlinks = false;
|
|
|
|
let _diags = with_time_budget(Duration::from_secs(10), "symlink loop follow=false", || {
|
|
scan_no_index(root, &cfg).expect("scan must not error on cyclic symlink with follow=false")
|
|
});
|
|
}
|
|
|
|
/// Mutually-referencing symlinks (`dirA/link -> ../dirB`, `dirB/link -> ../dirA`)
|
|
/// are the second common loop shape. Like the self-loop, this must terminate.
|
|
#[cfg(unix)]
|
|
#[test]
|
|
fn mutual_symlink_loop_does_not_hang() {
|
|
use nyx_scanner::scan_no_index;
|
|
use std::os::unix::fs::symlink;
|
|
|
|
let tmp = tempfile::tempdir().unwrap();
|
|
let root = tmp.path();
|
|
|
|
std::fs::write(root.join("real.js"), b"var x = 1;\n").unwrap();
|
|
|
|
let dir_a = root.join("dirA");
|
|
let dir_b = root.join("dirB");
|
|
std::fs::create_dir(&dir_a).unwrap();
|
|
std::fs::create_dir(&dir_b).unwrap();
|
|
std::fs::write(dir_a.join("a.js"), b"var a = 1;\n").unwrap();
|
|
std::fs::write(dir_b.join("b.js"), b"var b = 2;\n").unwrap();
|
|
symlink("../dirB", dir_a.join("to_b")).unwrap();
|
|
symlink("../dirA", dir_b.join("to_a")).unwrap();
|
|
|
|
let mut cfg = hostile_cfg();
|
|
cfg.scanner.follow_symlinks = true;
|
|
|
|
let _diags = with_time_budget(Duration::from_secs(10), "mutual symlink loop", || {
|
|
scan_no_index(root, &cfg).expect("scan must terminate on mutual symlink cycle")
|
|
});
|
|
}
|