Skip to content
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

URL with a path and credentials is not handled correctly #103

Merged
merged 2 commits into from
Mar 11, 2024

Conversation

msmania
Copy link
Contributor

@msmania msmania commented Mar 11, 2024

This is a fix for a regression introduced by 1766e70.

If a URL with a path is passed to JsonRpcProvider, the path is dropped when the provider makes a query because const url = new URL(route, finalRpcUrl); does drop the path in finalRpcUrl.

The proposed fix to create a URL first, and appends a path via string concat. This patch also adds a testcase for that logic.

Copy link

gitguardian bot commented Mar 11, 2024

⚠️ GitGuardian has uncovered 5 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
9967853 Triggered Base64 Basic Authentication 063a93e packages/provider/tests/json-rpc-provider.test.ts View secret
9967853 Triggered Base64 Basic Authentication 122375b packages/provider/tests/json-rpc-provider.test.ts View secret
9967854 Triggered Basic Auth String 063a93e packages/provider/tests/json-rpc-provider.test.ts View secret
9967854 Triggered Basic Auth String 122375b packages/provider/tests/json-rpc-provider.test.ts View secret
9967854 Triggered Basic Auth String 122375b packages/provider/tests/json-rpc-provider.test.ts View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!

@msmania msmania requested a review from nodiesBlade March 11, 2024 20:26
@msmania msmania self-assigned this Mar 11, 2024
@msmania msmania added the bug Something isn't working label Mar 11, 2024
Copy link
Contributor

@nodiesBlade nodiesBlade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@msmania msmania merged commit b73415d into main Mar 11, 2024
3 of 4 checks passed
@msmania msmania deleted the toshi/bugfix-url-with-path branch March 11, 2024 22:57
@msmania
Copy link
Contributor Author

msmania commented Mar 11, 2024

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: In Progress
Development

Successfully merging this pull request may close these issues.

2 participants