fix(auth): reject malformed bearer credentials - #1638
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
betegon
marked this pull request as ready for review
September 28, 2026 10:31
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
betegon
force-pushed
the
bt/fix-auth-token-leaks
branch
from
September 28, 2026 10:44
bc20791 to
9a22d3c
Compare
betegon
changed the title
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9a22d3c. Configure here.
BYK
requested changes
Sep 28, 2026
Member
Author
|
both comments addressed! @BYK |
BYK
requested changes
Sep 28, 2026
BYK
approved these changes
Sep 28, 2026
betegon
added a commit
that referenced
this pull request
Sep 29, 2026
## Summary Runtime errors can echo credentials into command diagnostics. Redact recognizable Sentry tokens and Bearer values in CLI/Stricli errors, SDK errors, and outgoing telemetry envelopes, including credentials split by control characters or escaped in JSON. Telemetry redaction runs at the final transport boundary, after scope attributes and internal errors are resolved. A detached JSON copy preserves SDK serialization behavior without mutating caller objects or live SDK state. Text redaction has no SDK dependencies, preserving the completion startup path. Fatal diagnostics retain error names while redacting credentials. This complements the merged auth validation in #1638: diagnostics can still contain credentials from custom headers and other error paths. ## Validation - Full unit suite: 10,143 passed, 14 skipped (`TZ=UTC`). - 35 auth/library/completion E2E tests passed against a fresh bundle. - Lint, typecheck, bundle build, and diff checks passed. - Regression tests failed before these fixes and passed afterward: both CLI/library entry points avoid eager SDK imports, and the actual fatal handler preserves the error name and redacts split credentials. - Factored regex sources and flags match the previous implementation exactly; envelope redaction was moved without behavior changes. ## Limits Redaction recognizes Sentry token prefixes and Bearer context; it does not detect arbitrary opaque secrets without that context. Binary attachment bytes are preserved. Successful API response formatting is unchanged. Runtime header errors can contain ambiguous delimiters inside the credential itself. Redaction conservatively uses the final matching delimiter, which can also hide intervening text when multiple diagnostics are concatenated into one string.
This branch was successfully deployed
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
2 participants
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.
Summary
Malformed bearer credentials can be echoed by runtime header-validation errors. Normalize access tokens and reject invalid formatting before constructing authenticated API, Docs, init, and artifact-download requests. Failures use a fixed
AUTH_INVALIDmessage without the credential and preserve exit code 12.Share one helper for trimming surrounding whitespace and ASCII controls. Internal whitespace, controls, and non-ASCII characters remain invalid; split lines are never joined. Environment selection, token host claims, and cache
Varymetadata use the same trimming rules. Cache metadata only trims a candidate: validation waits until OAuth refresh and credential selection determine the token actually used.Validate access tokens before SQLite writes, including refreshed credentials. Reject a malformed explicit
auth login --tokenbefore changing the host or clearing existing authentication. Legacy JSON migration skips malformed auth, migrates other settings, and retains the original file with a fixed recovery warning, so help, login, and logout remain usable.Malformed-token failures remain visible as safe
MalformedAuthTokenErrorevents without retaining the credential or original cause. They do not trigger auto-login or mark a session crashed; ordinary authentication failures keep their existing reporting policy.Validation
e754fb328: 467 unit files, 10,050 passed / 14 skipped (TZ=UTC); 34 bundled E2E passed across auth, library, and migration; lint, TypeScript, and bundle build passed.git diff --check. Production code is unchanged; the full suite and build were not repeated locally.Separate work
General output and telemetry redaction remains in #1640. SDK invocation isolation (#1645) and rc tokens truncated when copied into
process.env(#1646) are separate fixes; this PR does not address those earlier input/lifecycle boundaries.Bundler consumers pinned to
sentry ^0.44.0need a0.44.xbackport or a dependency update after release.