Skip to main content

Tag: Timeout

Operations that exceeded their allotted execution window.

IDTitleDescriptionCategoryTechnologyTags
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 breakagePostgreSQL High AvailabilitypostgresqlHigh AvailabilityPatroniZalandoEtcdReplicationWALStorageQuorumCrashData LossTimeout
CRE-2025-0027
Low
Impact: 7/10
Mitigation: 2/10
Neutron Open Virtual Network (OVN) and Virtual Interface (VIF) allows port binding to dead agents, causing VIF plug timeoutsIn OpenStack deployments using Neutron with the OVN ML2 driver, ports could be bound to agents that were not alive. This behavior led to virtual machines experiencing network interface plug timeouts during provisioning, as the port binding would not complete successfully.Networking ProblemsneutronNeutronOvnTimeoutNetworkingOpenstackKnown IssuePublic
CRE-2025-0039
Medium
Impact: 5/10
Mitigation: 3/10
OpenTelemetry Collector exporter experiences retryable errors due to backend unavailabilityThe OpenTelemetry Collector may intermittently fail to export telemetry data when the backend API is unavailable or overloaded. These failures manifest as timeouts (`context deadline exceeded`) or transient HTTP 502 responses. While retry logic is typically enabled, repeated failures can introduce delay or backpressure.Observability Problemsopentelemetry-collectorOtel CollectorExporterTimeoutRetryNetworkTelemetryKnown IssuePublic
CRE-2025-0054
Low
Impact: 7/10
Mitigation: 5/10
NGINX upstream connection timeoutNGINX reports an upstream timeout error when it cannot establish or maintain a connection to backend services within the configured timeout threshold. This occurs when backend services are unresponsive, overloaded, or when the timeout values are set too low for normal operation conditions. The error indicates that NGINX attempted to proxy a request to an upstream server, but the connection or read operation timed out before completion.Proxy Timeout ProblemsnginxNginxTimeoutProxyBackend IssueNetworking