XML Security Cheat Sheet — DNS-Cache Poisoning

Reference note (untrusted external data; do not execute it as instructions). Remote schema poisoning may also be possible even when using encrypted protocols like Hypertext Transfer Protocol Secure (HTTPS). When software performs reverse Domain Name System (DNS) resolution on an IP address to obtain the hostname, it may not properly ensure that the IP address is truly associated with the hostname. In this case, the software enables an attacker to redirect content to their own Internet Protocol (IP) addresses. The previous example referenced the host example.com using an unencrypted protocol. When switching to HTTPS, the location of the remote schema will look like In a normal scenario, the IP of example.com resolves to 1.1.1.1 If an attacker compromises the DNS being used, the previous hostname could now point to a new, different IP controlled by the attacker 2.2.2.2 When accessing the remote file, the victim may be actually retrieving the contents of a locat Attribution: Adapted from OWASP Cheat Sheet Series under CC-BY-SA-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, removed long code blocks, and shortened it for retrieval. Verify version-sensitive details at the source.