Introduce Shared-Secret Authentication and Mitigate Node Registration SSRF (Fixed #22, #23)#25
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
yulmwu
commented
Jun 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, there was no authentication mechanism for privileged APIs in either
sbxletorsbxorch, leading to issues such as #22. Additionally, a potential SSRF vulnerability in the orchestration layer during node registration (#23) was identified and addressed as part of this change.#22 — Shared-Secret Authentication
sbxorch,sbxlet, andsbxctlnow authenticate privileged APIs using a single static shared secret. Communication succeeds only if all three components are configured with the same secret.Configuration:
shared_secretin each config fileSBX_SHARED_SECRETenvironment variablesbxctladditionally supports the--secretflagOutbound requests (
sbxctltosbxorch,sbxorchtosbxlet) include anAuthorization: Bearer <secret>headerProtected routes return
401 Unauthorizedif the token does not match (using constant-time comparison)Public routes are limited to
GET /healthzand/swagger/*Fail-closed behavior:
sbxorchandsbxletrefuse to start ifshared_secretis not configuredNote
mTLS and similar mechanisms were considered, but ultimately deemed unnecessary for the current scale of this project, so they have been deferred for now.
#23 — Node Registration SSRF Hardening
Node registration now rejects IP addresses that are:
169.254.169.254)Loopback and private address ranges remain allowed, since they are valid node addresses.
Furthermore, unauthenticated node registration is now prevented through the authentication mechanism introduced in #22.
For more details, please refer to the changes included in this PR.
Contributors
sbxorchandsbxletHTTP Control APIs #22, Unrestricted Node Registration Enables Orchestrator-Side SSRF andsbxletProxying #23 (Vulnerability Reporter)