Skip to content

🛡️ Sentinel: Validate non-positive form IDs in year handlers - #247

Closed
d0linger wants to merge 1 commit into
mainfrom
jules-15734210251081677727-e3aa4f54
Closed

d0linger wants to merge 1 commit into
mainfrom
jules-15734210251081677727-e3aa4f54

Conversation

@d0linger

Copy link
Copy Markdown
Owner

🛡️ Sentinel Security PR: Validate non-positive base, year, and neighbor form IDs

  • Severity: MEDIUM
  • Vulnerability: Unvalidated non-positive numeric form parameters (base_id, year_id, neighbor_id) bypassing upfront validation checks and executing database queries/transactions.
  • Impact: Non-positive values (e.g. <= 0) could cause unexpected foreign key constraint errors or unconstrained database operations.
  • Fix: Enforced upfront non-positive checks (<= 0) in handleYearCreate, handleYearUpdate, handleYearAddNeighbor, handleYearRemoveNeighbor, and handleYearRolloverCreate before database calls.
  • Verification: Added TestYearIDValidation unit tests in internal/server/input_limits_test.go and verified with go test ./....

PR created automatically by Jules for task 15734210251081677727 started by @d0linger

Enforce upfront checks (<= 0) on base_id, year_id, and neighbor_id
parameters across year management, rollover, and neighbor association
endpoints to prevent unexpected database errors and unconstrained queries.

Co-authored-by: d0linger <61334677+d0linger@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 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 Oct 20, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

d0linger added a commit that referenced this pull request Oct 22, 2026
Apply input hardening from PRs #240-243, #247-248 and #250, consolidate
duplicate proposals, and adapt validation to the new accounting presets.
Update the matched browser packages/image and patched Go toolchains from
PRs #244-246 and #249 while preserving correct image digests.

Require passkey authentication when policy forbids password-only sign-in,
serialize signature changes with the open account/invoice boundary, and
keep audit verification consistent with concurrent sealing and pruning.
Reject overflowing form integers and add regression coverage.

Validate with the pinned linter, vet, dead-code and vulnerability scans,
PostgreSQL 16/18 race and integration suites, 208 browser tests and
40 existing screenshot baselines.
@d0linger

Copy link
Copy Markdown
Owner Author

Superseded by #251

@d0linger d0linger closed this Oct 23, 2026
@google-labs-jules

Copy link
Copy Markdown
Contributor

Superseded by #251

Understood. Acknowledging that this PR/task is superseded by #251 and stopping work on this task.

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