Zulip Slack Importer Bug Could Silently Scramble Message History Mid-Migration

A vulnerability in Zulip's Slack import tool caused migrations to either crash or silently disorder message history due to unguarded timestamp parsing in the Python codebase. When a message lacked a valid 'ts' timestamp field, the importer would abort the entire process mid-run, potentially halting migrations of tens of thousands of messages. More dangerously, a 'NaN' timestamp value would pass parsing without error, causing messages to sort incorrectly and leaving admins with a corrupted archive. A community contributor submitted fix PR #39813, which skips malformed timestamps with a warning and validates that parsed values are finite numbers using Python's math.isfinite. The patch addresses a robustness issue previously flagged in Zulip's own internal audit, affecting the data import subsystem that handles migrations from Slack, Microsoft Teams, and Mattermost.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in