Skip to content

🔒 [Security Fix] Remove insecure btoa fallback for webhook signatures#1210

Closed
Hardonian wants to merge 1 commit into
mainfrom
fix/webhook-crypto-fallback-11518528861325700310
Closed

🔒 [Security Fix] Remove insecure btoa fallback for webhook signatures#1210
Hardonian wants to merge 1 commit into
mainfrom
fix/webhook-crypto-fallback-11518528861325700310

Conversation

@Hardonian

Copy link
Copy Markdown
Owner

🎯 What: The WebhookManager in @settler/react-settler used an insecure btoa(message + this.secret) implementation to generate signatures in environments where crypto.subtle was unavailable.
⚠️ Risk: btoa only performs base64 encoding, providing no cryptographic security. An attacker could trivially forge webhook signatures by base64 encoding the payload with a guessed or empty secret, or recover the secret from a base64 decoded signature.
🛡️ Solution: Removed the insecure fallback completely and replaced it with a fast-fail exception (throw new Error(...)) that strictly enforces the requirement for a secure crypto implementation.


PR created automatically by Jules for task 11518528861325700310 started by @Hardonian

@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
settler Error Error Jul 17, 2026 5:06am

@github-actions

Copy link
Copy Markdown

🔒 Release Safety Check Results

Safety Checks Passed

{"code":"NOT_FOUND","message":"Requested function was not found"}

@github-actions

Copy link
Copy Markdown

🔍 Classification Check Results

  • Total Files: 5293
  • OSS_PUBLIC: 52 ✅
  • PLATFORM_PROPRIETARY: 104
  • INTERNAL_BUSINESS: 1644
  • SECRET_RISK: 0 ✅
  • Violations: 0 ✅

No violations detected. Safe to merge!


📊 View full classification report

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 51e1e795ad

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +142 to +144
throw new Error(
"Secure crypto implementation is required but not available in this environment."
);

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Regenerate shipped dist for webhook signing

In the published package path (main/exports point at dist/index.js, and files includes dist), consumers never execute this changed source unless they rebuild from source. Since packages/react-settler/dist/utils/webhooks.js still has return btoa(message + this.secret).substring(0, 64), installs from this commit keep the insecure fallback despite this change, so the security fix is ineffective for normal package consumers. Please regenerate/update the tracked dist output with the source change.

Useful? React with 👍 / 👎.

@Hardonian

Copy link
Copy Markdown
Owner Author

Closed during PR cleanup: mergeable=CONFLICTING base=main. Reopen only with a current verified change.

@Hardonian Hardonian closed this Jul 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant