Skip to content

fix: verify calendar webhook tokens and Zoom timestamp freshness - #942

Open
valvesss wants to merge 1 commit into
attendee-labs:mainfrom
cold-code-labs:fix/security-external-webhooks
Open

fix: verify calendar webhook tokens and Zoom timestamp freshness#942
valvesss wants to merge 1 commit into
attendee-labs:mainfrom
cold-code-labs:fix/security-external-webhooks

Conversation

@valvesss

@valvesss valvesss commented Aug 7, 2026

Copy link
Copy Markdown

Summary

  • Microsoft Calendar: verify clientState ({"calendar_id": …}); UUID alone ignored; batch uses continue not early return.
  • Google Calendar: verify X-Goog-Channel-Token.
  • Zoom: 5-minute timestamp freshness + hmac.compare_digest.
  • ZoomOAuthApp: missing encrypted credentials → None (no AttributeError).

Test plan

Local (Mimir): Postgres 15.3 + Redis 7.

  • Calendar + Zoom external webhooks + OAuth utils — 65/65 OK (spoof/stale/fresh/compare_digest)

Still for CI: same modules in project Docker test env.


Contribution from Cold Code Labs · authored via Brokk · co-authors in commit trailers.

Require Microsoft clientState and Google channel token to match the
calendar-bound secret set at subscription creation, keep processing
valid Microsoft batch items after invalid ones, and reject stale Zoom
webhook timestamps with constant-time signature compare.

Co-authored-by: Vitor Alves <vitoralvesinfo@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@valvesss
valvesss requested a review from a team as a code owner August 7, 2026 15:16
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.

2 participants