搜索结果
关于「bind9」的漏洞数据
| AVD编号 | 漏洞名称 | 漏洞类型 | 披露时间 | 漏洞状态 |
|---|---|---|---|---|
| AVD-2026-80274 | Validating resolver can abort while caching a mismatched NOQNAME proof(CVE-2026-80274) | 2026-09-16 | ||
| AVD-2026-77119 | NSEC3 insecure-referral proof can use unrelated cached NSEC3 RRsets(CVE-2026-77119) | 2026-09-16 | ||
| AVD-2026-75029 | BIND 9 内存放大漏洞(CVE-2026-75029) | 2026-09-16 | ||
| AVD-2026-19033 | Unauthenticated IXFR deltas are applied to the live zone before TSIG verification(CVE-2026-19033) | 2026-09-16 | ||
| AVD-2026-19668 | Resource Exhaustion via Excessive DNSSEC Cryptographic Material Matching(CVE-2026-19668) | 2026-09-16 | ||
| AVD-2026-19666 | Use-after-free in query_addnoqnameproof() via the DNS64 filter64 path(CVE-2026-19666) | 2026-09-16 | ||
| AVD-2026-81736 | Remote CPU denial of service through cached SVCB/HTTPS AliasMode trees(CVE-2026-81736) | 2026-09-16 | ||
| AVD-2026-81563 | SVCB AliasMode additional-data error leaks qpcache references(CVE-2026-81563) | 2026-09-16 | ||
| AVD-2026-78301 | Out-of-zone database nodes can become authoritative zone cuts(CVE-2026-78301) | 2026-09-16 | ||
| AVD-2026-19941 | checkwildcard() accepts an out-of-zone NSEC as a wildcard-nonexistence proof(CVE-2026-19941) | 2026-09-16 | ||
| AVD-2026-19667 | Remote assertion failure via 16-bit length truncation in `dns_ncache_add()`(CVE-2026-19667) | 2026-09-16 | ||
| AVD-2026-19662 | qpcache NOQNAME proof use-after-free crashes recursive resolver(CVE-2026-19662) | 2026-09-16 | ||
| AVD-2026-13321 | 通过区域外 NSEC Next 字段绕过 DNSSEC 验证 (CVE-2026-13321) | 2026-07-22 | ||
| AVD-2026-13204 | 在同时存在 NSEC 和 NSEC3 的某些情况下意外退出 (CVE-2026-13204) | 2026-07-22 | ||
| AVD-2026-10723 | 错误接受 NSEC3 记录 (CVE-2026-10723) | 2026-07-22 | ||
| AVD-2026-11331 | 潜在的通配符 CNAME RPZ 策略绕过 (CVE-2026-11331) | 2026-07-22 | ||
| AVD-2026-10822 | 使用 PRIVATEDNS 算法的密钥记录可能会导致意外退出 (CVE-2026-10822) | 2026-07-22 | ||
| AVD-2026-12617 | 使用 CNAME 或 DNAME 记录基于意外退出的排序 (CVE-2026-12617) | 2026-07-22 | ||
| AVD-2026-11721 | 标签计数差异、RRSIG 和通配符可能导致缓存中毒 (CVE-2026-11721) | 2026-07-22 | ||
| AVD-2026-11622 | 潜在内存使用超出配置限制 (CVE-2026-11622) | 2026-07-22 | ||
| AVD-2026-5946 | CLASS != IN 的处理无效 (CVE-2026-5946) | 2026-05-20 | ||
| AVD-2026-5950 | BIND 9 解析器中的无限重发循环 (CVE-2026-5950) | 2026-05-20 | ||
| AVD-2026-3592 | 通过自指向粘合记录放大漏洞 (CVE-2026-3592) | 2026-05-20 | ||
| AVD-2026-3039 | GSS-API TKEY 协商期间 BIND 9 服务器内存耗尽 (CVE-2026-3039) | 2026-05-20 | ||
| AVD-2026-1519 | BIND 9 DNSSEC 验证 CPU 耗尽漏洞(CVE-2026-1519) | 2026-03-25 | ||
| AVD-2025-8677 | 格式错误的 DNSKEY 处理导致资源耗尽 (CVE-2025-8677) | 2025-10-23 | ||
| AVD-2025-40780 | 由于 PRNG 较弱而导致缓存中毒 (CVE-2025-40780) | 2025-10-23 | ||
| AVD-2025-40778 | 使用未经请求的 RR 进行缓存中毒攻击 (CVE-2025-40778) | 2025-10-23 | ||
| AVD-2024-12705 | DNS-over-HTTPS 实现在高查询负载下存在多个问题（CVE-2024-12705） | 2025-01-30 | ||
| AVD-2024-11187 | 附加部分中的许多记录导致 CPU 耗尽（CVE-2024-11187） | 2025-01-30 |