Skip to content

harden: add magic validation and buffer bounds to parseEngine/parseConfig#196

Open
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:harden/parseEngine-magic-and-bounds
Open

harden: add magic validation and buffer bounds to parseEngine/parseConfig#196
0x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
0x-SquidSol:harden/parseEngine-magic-and-bounds

Conversation

@0x-SquidSol
Copy link
Copy Markdown
Contributor

Summary

  • parseEngine and parseConfig can be called directly from adl.ts without going through parseHeader (which validates PERCOLAT magic)
  • A malicious RPC returning arbitrary bytes matching a known slab size would be silently parsed into garbage engine state (vault balances, PnL, oracle data) or config (collateral mint, oracle authority)
  • parseEngine also had zero buffer bounds checking — truncated RPC data would produce either garbage BigInts (silent wrong values) or cryptic DataView RangeError with no context

Additions:

  • PERCOLAT magic check at the top of both parseEngine and parseConfig — one readU64LE comparison, zero overhead for valid slabs
  • Buffer bounds check in parseEngine: data.length < layout.accountsOff ensures the buffer covers the entire engine section before any field reads

Test plan

  • No new test failures (729 passed, same 16 pre-existing)
  • All test mock slabs include PERCOLAT magic at offset 0 — zero false positives
  • All test buffers are full-tier-sized — bounds check never trips on valid data

🤖 Generated with Claude Code

…nfig

parseEngine and parseConfig could be called directly (e.g., from
adl.ts) without going through parseHeader which validates magic.
A malicious RPC returning arbitrary bytes matching a known slab
size would be silently parsed into garbage engine/config state.

parseEngine also had no buffer bounds check — truncated RPC data
would produce either garbage BigInts (silent) or cryptic DataView
RangeErrors (no context).

Added:
- PERCOLAT magic check to both parseEngine and parseConfig
- Buffer bounds check to parseEngine (data.length < accountsOff)
  catches truncation before any engine field reads

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 13, 2026

Warning

Rate limit exceeded

@0x-SquidSol has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 45 minutes and 14 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 45 minutes and 14 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: febb593e-9455-4024-b798-ed33a3ef99db

📥 Commits

Reviewing files that changed from the base of the PR and between 2f80d79 and 9764e1b.

📒 Files selected for processing (1)
  • src/solana/slab.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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 and usage tips.

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