Skip to content

preserve(security): zero-delta TemporalAnalyzer log-injection provenance pending #1055 - #1229

Draft
seonghobae wants to merge 12 commits into
developfrom
fix/log-injection-vulnerabilities-404772855862254541
Draft

seonghobae wants to merge 12 commits into
developfrom
fix/log-injection-vulnerabilities-404772855862254541

Conversation

@seonghobae

@seonghobae seonghobae commented Sep 17, 2026

Copy link
Copy Markdown
Collaborator

Preservation / succession status

This branch is provenance only; it is not an independent TemporalAnalyzer privacy source owner.

The original generated repr(path) repair escaped control characters but still disclosed the selected local path and rendered decoder-controlled exception text. A later continuation moved toward path-free logging and added a narrow regression, but both the production behavior and useful evidence are already represented more strongly in #1055: canonical progress/failure logs exclude the source path, expose only generic selected-local-audio context plus exception type, and its caplog regression forces a decoder failure whose message contains the selected path and requires that path to remain absent.

#1237 separately preserves the distinct broken-__str__ / oversized caller-visible diagnostic finding; it must be adopted later without reintroducing path/filename logging or the temporary CLI probe.

Ordinary non-force descendant 4d9df539... keeps all generated continuations in ancestry and restores the protected tree. This branch now carries no parallel runtime/test/metadata source.

PR-0 / closure rule

Keep Open / Draft until #1055 or a verified successor has adopted every valid #1211/#1237 diagnostic delta, preserved the stronger path-free/orchestration contract, obtained fresh exact-head repository/security/SAST/SBOM/CodeQL evidence plus qualifying independent non-author approval, and reached protected ancestry. Only then may this zero-delta provenance lane be closed unmerged.

No self-approval, force-push, destructive rebase, raw/escaped path logging, decoder-text logging, duplicate temporal source, copied formatter source, gate weakening, blind rerun, no-op freshness commit, synthetic status, predecessor-evidence transfer, or premature Close.

@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@coderabbitai

coderabbitai Bot commented Sep 17, 2026

Copy link
Copy Markdown
Contributor

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: d978dd10-a38c-422a-8204-cc486b92ba03

📥 Commits

Reviewing files that changed from the base of the PR and between 314ddea and f65d132.

📒 Files selected for processing (2)
  • .jules/sentinel.md
  • services/analysis-engine/src/bandscope_analysis/temporal/analyzer.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

TemporalAnalyzer.analyze의 세 로그 호출을 지연 % 보간 방식으로 변경했습니다. 경로 입력에는 repr()을 적용했습니다. 로그 주입 방지 지침을 문서에 추가했습니다.

Changes

로그 안전성 개선

Layer / File(s) Summary
안전한 로그 포맷 적용
.jules/sentinel.md, services/analysis-engine/src/bandscope_analysis/temporal/analyzer.py
로그 주입 방지 지침을 추가했습니다. 로딩, 완료, 오류 로그를 지연 % 보간 방식으로 변경했습니다. 경로 입력에는 repr()을 적용했습니다. 분석 로직과 오류 처리는 변경하지 않았습니다.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Bug fix

Merge Risk: ⚪ Minimal · up to f65d1

The logging-only change safely represents the request-derived path, with no demonstrated merge-blocking regression.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 …
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed 제목은 TemporalAnalyzer의 로그 인젝션 보안 변경을 명확히 지칭합니다. 변경 내용과 직접 관련되며 주요 목적을 요약합니다.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/log-injection-vulnerabilities-404772855862254541

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae marked this pull request as draft September 17, 2026 05:04
@seonghobae seonghobae added bug Something isn't working priority: high High-priority or P1 work labels Sep 19, 2026 — with ChatGPT Codex Connector
seonghobae and others added 3 commits September 23, 2026 07:09
…formatter drift

Restore the validated preservation tree while retaining the intervening commit in ancestry. The only reverted delta is the unrelated Ruff-only supply-chain policy formatting owned by #1176; TemporalAnalyzer preservation evidence remains unchanged.

Signed-off-by: Seongho Bae <me@seonghobae.me>
Comment thread services/analysis-engine/tests/test_temporal.py Fixed
…rvation lane

Restore the validated #1229 preservation tree while retaining the generated test commit in ancestry. The intervening test asserted repr(path) disclosure as safe, which conflicts with canonical #1055 path-free logging and would encode the weaker implementation as expected behavior.

Signed-off-by: Seongho Bae <me@seonghobae.me>
@seonghobae seonghobae changed the title 🛡️ Sentinel: [MEDIUM] Fix log injection vulnerabilities in TemporalAnalyzer preserve(security): route TemporalAnalyzer log-injection finding to #1055 Sep 23, 2026
seonghobae and others added 2 commits September 24, 2026 02:31
Retain the generated regression commit in ancestry while removing the test that treats repr(path) disclosure as safe. Canonical #1055 keeps local-audio paths out of the log sink; this preservation lane must not encode the weaker disclosure contract as expected behavior.

Signed-off-by: Seongho Bae <me@seonghobae.me>

Copy link
Copy Markdown
Collaborator Author

Current authority update: fresh generated head 6d267a9ef4af319d94469666fb536824e16d742c added a regression that explicitly treats repr(path) disclosure as the safe logging contract (fake_logger.info(..., repr(str(test_wav)))). That conflicts with canonical #1055's stronger path-free log-sink privacy boundary and would encode the weaker generated implementation as expected behavior. Ordinary descendant 718091d7c23459b6a5c3c3c0115aa63f866e1e57 uses 6d267a9... as parent and restores validated preservation tree 8f7cebfc0f4eaefd76cdd9c32c497afd7fef87f9. Branch advanced with force=false; generated history remains ancestry. This lane remains Draft preservation evidence only; canonical adoption must keep raw/escaped source path and decoder exception text out of the log sink.

@google-labs-jules

Copy link
Copy Markdown

Current authority update: fresh generated head 6d267a9ef4af319d94469666fb536824e16d742c added a regression that explicitly treats repr(path) disclosure as the safe logging contract (fake_logger.info(..., repr(str(test_wav)))). That conflicts with canonical #1055's stronger path-free log-sink privacy boundary and would encode the weaker generated implementation as expected behavior. Ordinary descendant 718091d7c23459b6a5c3c3c0115aa63f866e1e57 uses 6d267a9... as parent and restores validated preservation tree 8f7cebfc0f4eaefd76cdd9c32c497afd7fef87f9. Branch advanced with force=false; generated history remains ancestry. This lane remains Draft preservation evidence only; canonical adoption must keep raw/escaped source path and decoder exception text out of the log sink.

Understood. Acknowledging that this work is now obsolete and stopping work on this task. The PR will not be updated further since the preservation lane should not encode the weaker path disclosure.

seonghobae and others added 2 commits September 24, 2026 03:18
…-only

Remove the duplicate TemporalAnalyzer/sentinel/test delta from the active diff. Canonical #1055 already owns the stronger path-free log sink and a stricter caplog regression covering decoder failure without local-path disclosure; #1237 preserves the separate bounded caller-visible diagnostic finding. Keep this branch history as provenance until verified protected succession satisfies PR-0.

Signed-off-by: Seongho Bae <me@seonghobae.me>
@seonghobae seonghobae changed the title preserve(security): route TemporalAnalyzer log-injection finding to #1055 preserve(security): zero-delta TemporalAnalyzer log-injection provenance pending #1055 Sep 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working priority: high High-priority or P1 work

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant