Improperly Trusted Reverse DNS |
Weakness ID: 350 (Weakness Base) | Status: Draft |
Description Summary
The software trusts the hostname that is provided when performing a reverse DNS resolution on an IP address, without also performing forward resolution.
Example 1
In the example below, an authorization decision is made on the result of a reverse DNS lookup.
(Bad Code)
Example Language: Java
InetAddress clientAddr = getClientInetAddr();
if (clientAddr != null && clientAddr.getHostName().equals("authorizedhost.authorizeddomain.com") {
authorized = true;
}
Reference | Description |
---|---|
CVE-2001-1488 | Does not do double-reverse lookup to prevent DNS spoofing. |
CVE-2001-1500 | Does not verify reverse-resolved hostnames in DNS. |
CVE-2000-1221 | Authentication bypass using spoofed reverse-resolved DNS hostnames. |
CVE-2002-0804 | Authentication bypass using spoofed reverse-resolved DNS hostnames. |
CVE-2001-1155 | Filter does not properly check the result of a reverse DNS lookup, which could allow remote attackers to bypass intended access restrictions via DNS spoofing. |
CVE-2004-0892 | Reverse DNS lookup used to spoof trusted content in intermediary. |
CVE-2003-0981 | Product records the reverse DNS name of a visitor in the logs, allowing spoofing and resultant XSS. |
Nature | Type | ID | Name | View(s) this relationship pertains to |
---|---|---|---|---|
ChildOf | Weakness Class | 345 | Insufficient Verification of Data Authenticity | Development Concepts (primary)699 Research Concepts (primary)1000 |
Submissions | ||||
---|---|---|---|---|
Submission Date | Submitter | Organization | Source | |
PLOVER | Externally Mined | |||
Modifications | ||||
Modification Date | Modifier | Organization | Source | |
2008-07-01 | Sean Eidemiller | Cigital | External | |
added/updated demonstrative examples | ||||
2008-09-08 | CWE Content Team | MITRE | Internal | |
updated Relationships, Taxonomy Mappings | ||||
2009-05-27 | CWE Content Team | MITRE | Internal | |
updated Relationships |