fix(destination): reject non-digit proxy port prefixes - #159
Conversation
|
Warning Review limit reached
Next review available in: 59 minutes Limit details: You’ve used all 1 included review currently available under your plan. 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?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthrough프록시 포트 파서는 숫자 범위 검증 전에 ASCII 십진수 형식을 확인합니다. Changes프록시 포트 검증
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The PR makes a localized proxy-port validation change with no actionable merge-blocking risk remaining beyond normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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 |
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
Buyer/security gap
OriginWeave's explicit proxy authority parsed proxy ports with Rust integer syntax before constructing its validation origin. Rust accepts a leading
+, while browser URL-style port syntax admits ASCII decimal digits only. Protected main could therefore admit identifiers such ashttp://proxy.example:+8080, creating a parser-authority mismatch at the proxy trust boundary.TDD lineage
This branch starts directly from protected main
0c376acf059be9ddddddfbde1d0189e4f39ef014.Exact test-only head
a9d432044c549c1926ee56143f1b3e8ca07e9ac3added scheme-less HTTP, explicit HTTP/HTTPS, SOCKS5, and bracketed IPv6 regressions requiring leading-plus port spellings to fail asProxyServerError::InvalidIdentifierbefore production changed. The current implementation then adds the narrow parser-local ASCII-decimal check and retains zero/out-of-range rejection.Implemented boundary
Current exact head
adb09a40699a70b7c7e252cd88dec42d41833b1f:u16parsing;CHANGELOG.md.The exact three-file diff is limited to the proxy parser, its focused integration regression, and the canonical changelog entry.
Exact-head verification
On unchanged exact head
adb09a40699a70b7c7e252cd88dec42d41833b1fagainst exact protected main0c376acf059be9ddddddfbde1d0189e4f39ef014:31836561095: success;94884100756: repository contracts, formatting, locked workspace/all-target checks, full tests, strict Clippy, and rustdoc success;94884100898: exact owned-production function, line, region, and branch coverage enforcement success;31836561124: success;31836561125: success;No queued, skipped, synthetic, predecessor-head, or model-only result is promoted as current proof.
Scope boundary
This changes no DNS, destination classification, socket, TLS, PAC evaluation, workflow, secret, persistence, browser execution, or release behavior. It is independently defensive from the canonical-origin parser fix in #158.
Passing automation is not independent approval. Protected integration remains subject to the live ruleset and unchanged-head review evidence.