-
Notifications
You must be signed in to change notification settings - Fork 15
security: reject foreign-host URLs in api to prevent token leak
#478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jeremy
wants to merge
1
commit into
main
Choose a base branch
from
security/01-api-token-leak
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+97
−17
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The accepted-behavior here looks intentional rather than a gap: this PR added the assertion together with an explanatory comment —
// Same host but no account segment — accepted, path used as-is.— so the description is the stale part, not the code.The contract in the description (
https://<host>/<numeric-account-id>/...) describes the original shape-based design. Over the course of review this became a host-based check (EqualFold(u.Host, base.Host)), which relocated the security property from 'does it have the account-id shape?' to 'is the host the one we're authenticated against?'. The account segment is irrelevant to the token-leak goal — only the host determines where the credential is sent.Keeping the lenient acceptance is also the more consistent choice:
api get projects.jsonandapi get https://<configured-host>/projects.jsonare the same effective request (same host, path/projects.json, SDK re-prefixes the account). Rejecting the second while accepting the first would be arbitrary, and tightening the code would reject a harmless, equivalent input.Recommend resolving this by updating the description to 'relative paths, or absolute URLs on the configured Basecamp host (foreign hosts rejected)' rather than changing the code. Leaving this for @jeremy to make the call.