Tag: WAL
Issues with Write-Ahead Logging in databases.
| ID | Title | Description | Category | Technology | Tags |
|---|---|---|---|---|---|
| CRE-2025-0020 High Impact: 10/10 Mitigation: 6/10 | Self-hosted PostgreSQL HA: WAL Streaming & HA Controller Crisis (Replication Slot Loss, Disk Full, Etcd Quorum Failure) | Detects high-severity failures in self-hosted PostgreSQL high-availability clusters managed by Patroni, Zalando, or similar HA controllers. This rule targets catastrophic conditions that break replication or cluster consensus: - WAL streaming failures due to missing replication slots (usually after disk full or crash events) - Persistent errors resolving HA controller endpoints (etcd/consul) and loss of HA controller quorum - Disk saturation leading to WAL write errors and replication breakage | PostgreSQL High Availability | postgresql | High AvailabilityPatroniZalandoEtcdReplicationWALStorageQuorumCrashData LossTimeout |
| CRE-2025-0141 High Impact: 10/10 Mitigation: 7/10 | Supabase Self-Hosted: Disk Full During Database Migration Operations | Detects when Supabase PostgreSQL database operations fail due to insufficient disk space during migrations, data imports, or large transactions. This can corrupt the database, leave migrations in inconsistent state, and cause complete service failure requiring manual intervention. | Storage | supabase | SupabasePostgreSQLDisk FullStorageMigration FailureWALSelf-HostedCritical FailureData Loss RiskPublic |