CWE · MITRE source
CWE-350Reliance on Reverse DNS Resolution for a Security-Critical Action
The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.
Since DNS names can be easily spoofed or misreported, and it may be difficult for the product to detect if a trusted DNS server has been compromised, DNS names do not constitute a valid authentication mechanism. When the product performs a reverse DNS resolution for an IP address, if an attacker controls the DNS server for that IP address, then the attacker can cause the server to return an arbitrary hostname. As a result, the attacker may be able to bypass authentication, cause the wrong hostname to be recorded in log files to hide activities, or perform other attacks. Attackers can spoof DNS names by either (1) compromising a DNS server and modifying its records (sometimes called DNS cache poisoning), or (2) having legitimate control over a DNS server associated with their IP address.
Last updated: 16 October 2026 14:24 UTC
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-1490 UPD | 7.5 | 9.8 | 0.0128 | 2026-02-15 |
CVE-2026-57123 | 7.5 | 9.8 | 0.0090 | 2026-09-14 |
CVE-2018-7160 UPD | 7.4 | 8.8 | 0.0987 | 2018-05-17 |
CVE-2021-22884 UPD | 7.4 | 7.5 | 0.3684 | 2021-03-03 |
CVE-2026-61568 UPD | 6.8 | 9.6 | 0.0053 | 2026-09-15 |
CVE-2017-0902 UPD | 6.7 | 8.1 | 0.0475 | 2017-08-31 |
CVE-2023-52235 UPD | 6.6 | 8.8 | 0.0054 | 2024-04-05 |
CVE-2026-42559 UPD | 6.4 | 8.8 | 0.0024 | 2026-05-14 |
CVE-2025-8036 UPD | 6.1 | 8.1 | 0.0043 | 2025-07-22 |
CVE-2026-55526 UPD | 6.1 | 8.5 | 0.0036 | 2026-08-25 |
CVE-2026-97875 | 6.0 | 8.1 | 0.0026 | 2026-09-25 |
CVE-2021-34561 UPD | 5.9 | 7.5 | 0.0087 | 2021-08-31 |
CVE-2026-24281 UPD | 5.8 | 7.4 | 0.0065 | 2026-03-07 |
CVE-2026-56709 UPD | 5.8 | 7.5 | 0.0043 | 2026-08-25 |
CVE-2026-33002 | 5.7 | 7.5 | 0.0046 | 2026-03-18 |
CVE-2026-55391 UPD | 5.4 | 7.5 | 0.0031 | 2026-07-28 |
CVE-2026-28271 | 5.2 | 6.5 | 0.0056 | 2026-02-27 |
CVE-2025-59956 UPD | 5.1 | 6.5 | 0.0043 | 2025-09-30 |
CVE-2024-42364 UPD | 5.0 | 6.5 | 0.0026 | 2024-08-23 |
CVE-2025-24010 UPD | 5.0 | 6.5 | 0.0029 | 2025-01-20 |
CVE-2025-61430 UPD | 5.0 | 6.5 | 0.0026 | 2025-10-24 |
CVE-2026-36604 UPD | 5.0 | 6.5 | 0.0035 | 2026-06-03 |
CVE-2026-75514 UPD | 4.8 | 5.9 | 0.0060 | 2026-08-20 |
CVE-2026-53708 UPD | 4.8 | 6.6 | 0.0035 | 2026-09-14 |
CVE-2026-61743 | 4.7 | 6.3 | 0.0040 | 2026-09-21 |