ThreatsDay: Adobe RCE, DNS 钱包盗窃, NVIDIA 容器逃逸, 自愈后门 + 另外 23 个 · 2h Silent Lynx 利用 WinRAR 漏洞在独立国家联合体政府攻击中部署反向 Shell · 5h NGINX 修复 5 个漏洞,包括可能的 RCE 和可能跳过客户端证书检查的 TLS 漏洞 · 8h Next.js 发布了针对缓存和 SVG 处理中的两个关键 RCE 漏洞的紧急补丁 · 8h Drupal 修补了通过贡献模块无需登录路径的关键核心 RCE 漏洞 · 9h Sparx Systems Enterprise Architect软件中的漏洞 · 9h Curl 修复了由 Anthropic 发现的“高” RCE 漏洞 · 9h Slican电话交换机中的漏洞 · 10h Palo Alto Networks警告防火墙安全漏洞被滥用 · 13h 思科报告称Secure Email Gateway中的关键漏洞被积极利用 · 14h ThreatsDay: Adobe RCE, DNS 钱包盗窃, NVIDIA 容器逃逸, 自愈后门 + 另外 23 个 · 2h Silent Lynx 利用 WinRAR 漏洞在独立国家联合体政府攻击中部署反向 Shell · 5h NGINX 修复 5 个漏洞,包括可能的 RCE 和可能跳过客户端证书检查的 TLS 漏洞 · 8h Next.js 发布了针对缓存和 SVG 处理中的两个关键 RCE 漏洞的紧急补丁 · 8h Drupal 修补了通过贡献模块无需登录路径的关键核心 RCE 漏洞 · 9h Sparx Systems Enterprise Architect软件中的漏洞 · 9h Curl 修复了由 Anthropic 发现的“高” RCE 漏洞 · 9h Slican电话交换机中的漏洞 · 10h Palo Alto Networks警告防火墙安全漏洞被滥用 · 13h 思科报告称Secure Email Gateway中的关键漏洞被积极利用 · 14h
🛡️
ACyber Sentinel 安全评估团队
← 返回
⚠️ 漏洞报告

CVE-2026-75806

CVE-2026-75806 - Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS

Issue summary: An established DTLS 1.2 association using an AEAD cipher suite

can be terminated by a single unauthenticated datagram whose encrypted

fragment is shorter than the mandatory explicit IV and authentication tag

overhead.

Impact summary: An attacker who can send a datagram that is routed to an

existing DTLS 1.2 association can tear that association down without knowing

any key material. This is a Denial of Service limited to the targeted

association. There is no memory safety or confidentiality impact.

CWE: CWE-1284: Improper Validation of Specified Quantity in Input

Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher

suite carries an explicit IV followed by the ciphertext and an authentication

tag. When decrypting such a record the record layer passed the record length to

the cipher implementation before checking that the record was long enough to

contain the explicit IV and the tag. For a record shorter than that overhead the

cipher implementation rejected the impossible length, and the record layer

treated this as an internal failure and raised a fatal internal_error alert

instead of treating the record as one that failed authentication.

In TLS 1.2 the same record causes a fatal internal_error alert instead of the

expected bad_record_mac alert. Since any undecryptable record already

terminates a TLS connection, this is a protocol conformance issue rather than

a security issue in TLS.

The fix validates the record length against the explicit IV and tag length

before any AEAD processing, so that TLS reports bad_record_mac and DTLS

silently discards the record.

FIPS impact: no

The affected code is outside the FIPS module boundary.

发布于: Sep 29, 2026 16:17

最后修改: Oct 08, 2026 01:20