๐ก๏ธ Sentinel: [CRITICAL] Fix CSV formula injection NUL byte bypass - #988
๐ก๏ธ Sentinel: [CRITICAL] Fix CSV formula injection NUL byte bypass#988seonghobae wants to merge 1 commit into
Conversation
|
๐ 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
Warning Review limit reached
Next review available in: 10 minutes Limit details: Youโve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?Wait for the limit to reset, then comment An organization admin can change what happens after included review limits in Billing. How do review limits work?CodeRabbit enforces per-developer PR review limits within each organization. For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window. Please refer docs for additional details. Review detailsโ๏ธ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: ๐ Files selected for processing (3)
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. Comment |
| // Prevent CSV formula injection by prefixing problematic leading characters with a single quote | ||
| if (/^[\s\uFEFF\xA0]*[=+\-@\t\r\n]/.test(value)) { | ||
| // eslint-disable-next-line no-control-regex | ||
| if (/^[\s\uFEFF\xA0]*[=+\-@\t\r\n\x00]/.test(value)) { |
There was a problem hiding this comment.
๐ Info: NUL added to trigger class, not leading class
\x00 was added to the trigger character class at export.ts rather than the leading-whitespace class named in the sentinel note. All NUL-prefix bypasses are still caught. One harmless side effect: a benign value like \x00hello now gets quote-prefixed.
Was this helpful? React with ๐ or ๐ to provide feedback.
|
Closing this lane as semantically superseded by canonical CSV-export security owner #941, after a fresh exact-head/base comparison. Evidence at close decision:
Do not merge or restack #988. Keep CSV formula-injection ownership on #941 and dependency-security ownership on #783; do not copy or suppress dependency findings in this lane. |
Understood. Acknowledging that this work is now obsolete and stopping work on this task. |
๐จ Severity: CRITICAL
๐ก Vulnerability: CSV formula injection mitigation was naive and could be bypassed if a NUL byte (
\x00) was prepended to the payload (e.g.,\x00=1+2).๐ฏ Impact: Attackers could inject formulas into CSV exports (like the cue sheet export) that would be evaluated by spreadsheet applications like Excel upon opening the file, leading to potential command execution or data exfiltration on the user's machine.
๐ง Fix: Updated the CSV formula injection prevention regex in
apps/desktop/src/lib/export.tsto include the\x00character in the class of leading whitespace/control characters. Explicitly added// eslint-disable-next-line no-control-regexto bypass linting errors for using a control character in a regex. Also added a unit test to verify this behavior and added an entry to.jules/sentinel.md.โ Verification: Ran unit tests for frontend (
npm run test --workspace @bandscope/desktop), backend (uv run pytest), and monorepo quickcheck (./scripts/harness/quickcheck.sh). All tests pass with 100% coverage.PR created automatically by Jules for task 17943981008591443344 started by @seonghobae