fix: URI-encode path parameters in API client request URLs (#1157) - #1240
Open
euniceamoni wants to merge 4 commits into
Open
fix: URI-encode path parameters in API client request URLs (#1157)#1240euniceamoni wants to merge 4 commits into
euniceamoni wants to merge 4 commits into
Conversation
PII (email address) was being sent as a URL query parameter on
GET /api/v1/newsletter/gdpr/export, exposing it to server access
logs, browser history, and proxy logs.
Changes:
- frontend: newsletterGdprExport now uses POST with body: { email }
instead of GET with params: { email } (client.ts)
- backend: added NewsletterExportBody struct, changed handler extractor
from Query to Json, updated utoipa path attribute to post,
updated route registration from get() to post() (handlers.rs, main.rs)
- tests: updated it.each entry to expect POST; added new test in
'GDPR export (solutions-plug#1156)' describe block asserting email is in the
request body and absent from the URL
Fixes solutions-plug#1156
Update openapi.yaml /api/v1/newsletter/gdpr/export from GET with query parameter to POST with requestBody (EmailRequest schema), matching the handler change in handlers.rs. Update SPEC_ROUTES in openapi_contract_test.rs from GET to POST to keep the contract test in sync with the spec and runtime router.
…-plug#1157) Wrap all path-segment interpolations with encodeURIComponent() to prevent path corruption and request-smuggling when values contain special characters (/, ?, #). Affected endpoints: getBlockchainMarket, getUserBets, getOracleResult, getTransactionStatus, resolveMarket, emailPreview. Add URI encoding test block (7 tests) covering all 6 endpoints and asserting that slash-containing values produce correctly encoded paths.
|
@euniceamoni Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
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
1 participant
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
Fixes #1157. Six API endpoints in
client.tsinterpolated caller-supplied values directly into URL path segments withoutencodeURIComponent(). Values containing/,?, or#would corrupt the request path and could be exploited as a path-manipulation / request-smuggling vector against the backend router.Changes
frontend/src/lib/api/client.ts— wrapped all path-segment interpolations withencodeURIComponent():getBlockchainMarket—marketIdgetUserBets—usergetOracleResult—marketIdgetTransactionStatus—txHashresolveMarket—marketIdemailPreview—templateNamefrontend/src/lib/api/__tests__/client.test.ts— addedURI encoding of path parameters (#1157)describe block with 7 tests covering all 6 affected endpoints plus a regression guard for plain values.Testing
All tests pass including the 7 new URI encoding tests.
cd frontend && npm run buildcompletes with zero warnings.Acceptance Criteria
/,?,#) no longer corrupt the resulting request pathPR Checklist
fix/path-parameters-are-interpolated-into-request-ur)cd frontend && npm run buildpasses with zero warningscd frontend && npm test -- client) closes [Bug] Path parameters are interpolated into request URLs without URI encoding #1157