Repeated Stalled TLS Handshakes via ALPN acme-tls/1 Extension
This rule detects two ALPN-based denial-of-service patterns against TLS servers. The first identifies repeated stalled handshakes advertising the acme-tls/1 ALPN extension with no session established, indicating…
Description
This rule detects two ALPN-based denial-of-service patterns against TLS servers. The first identifies repeated stalled handshakes advertising the acme-tls/1 ALPN extension with no session established, indicating potential goroutine or worker exhaustion in reverse proxies. The second matches connections where a malformed ALPN extension triggers TLS alerts such as decode_error or illegal_parameter, consistent with zero-length ALPN list exploitation. Both patterns are anomalous outside of scheduled ACME TLS-ALPN-01 certificate validation activity.
Detection logic
Its licence does not clear it for publishing here
Sunturai publishes a detection's own text where the licence it arrived under has been reviewed and permits it, and Elastic License 2.0 has not. The query as its source wrote it, its canonical form and the hash that pins this revision are in the workspace record.
Detection requirements
- Platform
- ContainersIaaSLinuxmacOSWindows
The rule states no platform. This is derived from the ATT&CK technique it maps to.
Known benign triggers
- Legitimate ACME certificate renewal agents (cert-manager, Certbot, Caddy) use acme-tls/1 during TLS-ALPN-01 challenges. A single incomplete challenge due to a network timeout can occur normally, but five or more incomplete sessions from the same source within the detection window is abnormal even for misconfigured ACME clients. TLS decode_error or illegal_parameter alerts can also be produced by buggy TLS clients or misconfigured load balancers. Suppress by adding known ACME client source IPs or ACME CA validation IP ranges to an exception list.
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| nvd.nist.gov/vuln/detail/CVE-2024-5535 | Only this detection cites it |
| nvd.nist.gov/vuln/detail/CVE-2026-22045 | Only this detection cites it |
| www.elastic.co/guide/en/beats/packetbeat/current/configuration-tls.html | 2 |
| www.rfc-editor.org/rfc/rfc8737 | Only this detection cites it |
From the source
- At source
- Open at source
- Upstream identifier
- 581bd9b4-ee08-415a-97d7-756e6c53c264
- Tagged by the source as
- Data Source: Network Packet CaptureData Source: Network TrafficDomain: NetworkNoise: UnknownPerformance: FastResources: Investigation GuideRule Type: ES|QLTactic: ImpactThreat: Vulnerability ExploitUse Case: Network Security MonitoringUse Case: Threat DetectionUse Case: Vulnerability
Licence
- Published under
- Elastic License 2.0Read the licence
- Attribution
- Required
Authorship
- Written by
- Published
- Sep 20, 2026
- Version
- 3