[workers-auth] Validate account IDs before using them in API requests - #13746
Conversation
🦋 Changeset detectedLatest commit: feb4369 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
✅ All changesets look good |
|
The analysis is complete. Let me now assess the overall quality of this PR: Summary: The PR validates account IDs from user-controlled sources (config file and environment variable) before they're used in API URL paths, preventing a confusing Assessment:
I don't see any logic bugs, security issues, backward compatibility problems, or incorrect API behavior. LGTM |
@cloudflare/autoconfig
@cloudflare/build-output-utils
@cloudflare/config
create-cloudflare
@cloudflare/deploy-helpers
@cloudflare/kv-asset-handler
miniflare
@cloudflare/pages-functions
@cloudflare/pages-shared
@cloudflare/unenv-preset
@cloudflare/vite-plugin
@cloudflare/vitest-pool-workers
@cloudflare/workers-auth
@cloudflare/workers-editor-shared
@cloudflare/workers-utils
wrangler
commit: |
|
Codeowners approval required for this PR:
Show detailed file reviewers
|
Account IDs are substituted straight into Cloudflare API URL paths, so a value containing non-ASCII characters failed deep inside the request layer with an opaque `Cannot convert argument to a ByteString` error. Validate `CLOUDFLARE_ACCOUNT_ID` and the consumer's `account_id` config field up front, and report which setting holds the offending value.
39f7d78 to
feb4369
Compare
|
Codeowners approval required for this PR:
Show detailed file reviewers |
workers-devprod
left a comment
There was a problem hiding this comment.
Codeowners reviews satisfied
Fixes #8380.
A picture of a cute animal (not mandatory, but encouraged)