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: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 3 mapping(s) from 2 framework(s): CAPEC 2 (partial) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A07:2025 Authentication Failures.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-1490 | 7.0 | 9.8 | 0.0116 | 2026-02-15 |
CVE-2021-22884 | 6.0 | 7.5 | 0.3236 | 2021-03-03 |
CVE-2017-0902 | 5.5 | 8.1 | 0.0475 | 2017-08-31 |
CVE-2018-7160 | 5.5 | 8.8 | 0.0992 | 2018-05-17 |
CVE-2021-34561 | 5.5 | 7.5 | 0.0087 | 2021-08-31 |
CVE-2023-52235 | 5.5 | 8.8 | 0.0053 | 2024-04-05 |
CVE-2025-8036 UPD | 5.5 | 8.1 | 0.0042 | 2025-07-22 |
CVE-2026-24281 UPD | 5.5 | 7.4 | 0.0062 | 2026-03-07 |
CVE-2026-33002 | 5.5 | 7.5 | 0.0030 | 2026-03-18 |
CVE-2026-42559 UPD | 5.5 | 8.8 | 0.0021 | 2026-05-14 |
CVE-2020-11091 | 3.5 | 5.8 | 0.0086 | 2020-06-03 |
CVE-2023-32020 | 3.5 | 5.6 | 0.0066 | 2023-06-14 |
CVE-2022-22364 | 3.5 | 5.3 | 0.0054 | 2024-05-03 |
CVE-2024-42364 | 3.5 | 6.5 | 0.0024 | 2024-08-23 |
CVE-2025-24010 | 3.5 | 6.5 | 0.0028 | 2025-01-20 |
CVE-2025-59956 | 3.5 | 6.5 | 0.0040 | 2025-09-30 |
CVE-2025-61430 | 3.5 | 6.5 | 0.0023 | 2025-10-24 |
CVE-2026-28271 | 3.5 | 6.5 | 0.0043 | 2026-02-27 |
CVE-2026-6874 | 3.5 | 4.3 | 0.0026 | 2026-04-23 |
CVE-2026-36604 UPD | 3.5 | 6.5 | 0.0025 | 2026-06-03 |
CVE-2026-46611 | 3.5 | 5.3 | 0.0016 | 2026-06-25 |