Jackh54 VoiceSentinel
VoiceSentinel: Race condition in report buffer cleanup can corrupt transcript data and cause unbounded disk growth
VoiceSentinel is a real-time voice moderation system for Minecraft servers. From 2.2.1 until 3.3.1, the optional report buffer feature has a race between retention cleanup and normal transcript writes. In `report_buffer.py`, `_maybe_cleanup()` uses an unlocked dictionary for once-per-hour cleanup throttling, allowing simultaneous `_cleanup_tenant()` operations for one tenant. Cleanup reads `transcripts.jsonl` and rewrites it in place without file locking or atomic replacement, while `report_buffer_append_async` uses `asyncio.to_thread` to append without synchronization. In `main.py`, concurrent `_processing_worker` tasks make this reachable in normal operation; `processing.worker_count` of two or more and public-pool servers sharing a `server_key` increase collisions. With `report_buffer.enabled` set to true, racing writes can lose, duplicate or corrupt transcript data and defeat `report_buffer.retention_seconds` pruning, allowing unbounded disk growth that can exhaust storage and crash the host or other services sharing it. The feature is opt-in and disabled by default. This issue is fixed in version 3.3.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.2.1, < 3.3.1
Fixed in 3.3.1
Mitigation
Upgrade VoiceSentinel to 3.3.1 or later.
References
- Vendor advisory github.com/jackh54/VoiceSentinel/security/advi…
- Patch github.com/jackh54/VoiceSentinel/commit/a8c9f9…
- Release notes github.com/jackh54/VoiceSentinel/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.