CVE-2026-54887: CWE-1394 Use of Default Cryptographic Key in Erlang OTP
Use of Default Cryptographic Key vulnerability in Erlang/OTP ssl (DTLS server) allows predictable DTLS cookie computation during the startup window, enabling source address verification bypass. On DTLS server startup, dtls_server_connection:initial_hello/3 initializes previous_cookie_secret to the empty binary (<<>>) instead of a random value. Because HMAC with an empty key is deterministic, anyone who observes the plaintext ClientHello can compute dtls_handshake:cookie(<<>>, IP, Port, Hello) and forge a valid DTLS cookie before the first rotation of the cookie secret. The DTLS cookie (RFC 6347 §4.2.1) is a denial-of-service mitigation that prevents spoofed source IPs from forcing the server to allocate state and perform expensive cryptographic operations; it is not an authentication mechanism. During the window from server startup until the first secret rotation (0 to 15 seconds), an attacker who can observe the plaintext ClientHello can bypass the source address verification, enabling DTLS handshake amplification with spoofed source addresses. This vulnerability is associated with program file lib/ssl/src/dtls_server_connection.erl and program routine dtls_server_connection:initial_hello/3. This issue affects OTP from OTP 20.0 before OTP 29.0.3, OTP 28.5.0.3 and OTP 27.3.4.14, corresponding to ssl from 8.2 before 11.7.3, 11.6.0.3 and 11.2.12.10.
AI Analysis
Technical Summary
This vulnerability arises because the DTLS server in Erlang/OTP initializes the previous_cookie_secret to an empty binary instead of a random value during startup. Since HMAC with an empty key is deterministic, an attacker who observes the ClientHello message can compute the DTLS cookie before the first secret rotation (which occurs within 0 to 15 seconds). This enables bypass of source address verification, allowing DTLS handshake amplification with spoofed source addresses during this startup window. The affected code is in lib/ssl/src/dtls_server_connection.erl, specifically the dtls_server_connection:initial_hello/3 function. The vulnerability affects OTP versions from 20.0 before 29.0.3, 28.5.0.3, and 27.3.4.14, corresponding to ssl versions from 8.2 before 11.7.3, 11.6.0.3, and 11.2.12.10.
Potential Impact
An attacker capable of observing plaintext ClientHello messages during the initial DTLS server startup window can bypass source address verification by forging valid DTLS cookies. This allows handshake amplification attacks with spoofed source IP addresses, potentially increasing denial-of-service risks. The DTLS cookie is not an authentication mechanism, so the impact is limited to denial-of-service amplification rather than unauthorized access or data compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, consider minimizing exposure during server startup or implementing network-level controls to limit spoofed traffic. Monitor vendor communications for updates on remediation.
CVE-2026-54887: CWE-1394 Use of Default Cryptographic Key in Erlang OTP
Description
Use of Default Cryptographic Key vulnerability in Erlang/OTP ssl (DTLS server) allows predictable DTLS cookie computation during the startup window, enabling source address verification bypass. On DTLS server startup, dtls_server_connection:initial_hello/3 initializes previous_cookie_secret to the empty binary (<<>>) instead of a random value. Because HMAC with an empty key is deterministic, anyone who observes the plaintext ClientHello can compute dtls_handshake:cookie(<<>>, IP, Port, Hello) and forge a valid DTLS cookie before the first rotation of the cookie secret. The DTLS cookie (RFC 6347 §4.2.1) is a denial-of-service mitigation that prevents spoofed source IPs from forcing the server to allocate state and perform expensive cryptographic operations; it is not an authentication mechanism. During the window from server startup until the first secret rotation (0 to 15 seconds), an attacker who can observe the plaintext ClientHello can bypass the source address verification, enabling DTLS handshake amplification with spoofed source addresses. This vulnerability is associated with program file lib/ssl/src/dtls_server_connection.erl and program routine dtls_server_connection:initial_hello/3. This issue affects OTP from OTP 20.0 before OTP 29.0.3, OTP 28.5.0.3 and OTP 27.3.4.14, corresponding to ssl from 8.2 before 11.7.3, 11.6.0.3 and 11.2.12.10.
CVSS v4.0
Score 6.3medium
Affected software
cpe:2.3:a:erlang:erlang\/otp:*:*:*:*:*:*:*:*Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
This vulnerability arises because the DTLS server in Erlang/OTP initializes the previous_cookie_secret to an empty binary instead of a random value during startup. Since HMAC with an empty key is deterministic, an attacker who observes the ClientHello message can compute the DTLS cookie before the first secret rotation (which occurs within 0 to 15 seconds). This enables bypass of source address verification, allowing DTLS handshake amplification with spoofed source addresses during this startup window. The affected code is in lib/ssl/src/dtls_server_connection.erl, specifically the dtls_server_connection:initial_hello/3 function. The vulnerability affects OTP versions from 20.0 before 29.0.3, 28.5.0.3, and 27.3.4.14, corresponding to ssl versions from 8.2 before 11.7.3, 11.6.0.3, and 11.2.12.10.
Potential Impact
An attacker capable of observing plaintext ClientHello messages during the initial DTLS server startup window can bypass source address verification by forging valid DTLS cookies. This allows handshake amplification attacks with spoofed source IP addresses, potentially increasing denial-of-service risks. The DTLS cookie is not an authentication mechanism, so the impact is limited to denial-of-service amplification rather than unauthorized access or data compromise.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch links are provided in the available data. Until a patch is available, consider minimizing exposure during server startup or implementing network-level controls to limit spoofed traffic. Monitor vendor communications for updates on remediation.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- EEF
- Date Reserved
- 2026-06-16T10:47:13.915Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a46a8b827e9c79719cc4ab5
Added to database: 07/02/2026, 18:06:48 UTC
Last enriched: 07/24/2026, 21:37:16 UTC
Last updated: 08/14/2026, 00:41:13 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.