Hostname validation and policy evasion prevention
A request to establish a session with a first server is received from a client device. The first server is associated with a first hostname, and the request includes information identifying a second hostname purported to correspond to the first server. A Domain Name System (DNS) lookup using the second hostname is performed. A determination that the second hostname was spoofed by the client device is determined based on a response to the DNS lookup. In response to the determination being made that the request received from the client device includes the spoofed second hostname, a determination that the client device has injected or overridden at least one of an HTTP Host header and a Server Name Indicator in the request is made, and an action to take with respect to the client device is determined.
1. A system, comprising:
a processor configured to:
receive, from a client device, a request to establish a session with a first server, wherein the first server is associated with a first hostname, and wherein the request includes information identifying a second hostname purported to correspond to the first server;
perform a Domain Name System (DNS) lookup using the second hostname, and determine that the second hostname was spoofed by the client device based on a response to the DNS lookup, wherein the response indicates that the first server is not associated with the second hostname; and
in response to determining that the request received from the client device includes the spoofed second hostname, determine that the client device has injected or overridden at least one of an HTTP Host header and a Server Name Indicator in the request, and determine an action to take with respect to the client device; and
a memory coupled to the processor and configured to provide the processor with instructions.
2. The system of claim 1 wherein the processor is further configured to determine that the client device has been compromised.
3. The system of claim 2 wherein the compromise includes mimicking a connection to a trusted service to evade at least one of a decryption and an inspection.
4. The system of claim 2 wherein the compromise includes concealing a connection to a command and control channel.
5. The system of claim 1 wherein the second hostname is included by the client device in the HTTP Host header in a client GET request.
6. The system of claim 1 wherein the second hostname is included by the client device in a Server Name Indicator in a TLS client hello.
7. The system of claim 1 wherein performing the DNS lookup includes querying a cache.
8. The system of claim 1 wherein determining that the second hostname was spoofed by the client device includes comparing a result of the DNS lookup to a destination IP address of a session between the client device and the first server.
9. The system of claim 1 wherein the DNS lookup is performed out of band from the client device establishing the session with the first server.
10. The system of claim 1 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, the client device is prevented from accessing the first server.
11. The system of claim 10 wherein the client device is prevented from accessing the first server by resetting an established session between the client device and the first server.
12. The system of claim 1 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, an alert is generated.
13. The system of claim 1 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, a log entry is generated.
14. The system of claim 1 wherein the processor is further configured to cache a result of the DNS lookup.
15. A method, comprising:
receiving, from a client device, a request to establish a session with a first server, wherein the first server is associated with a first hostname, and wherein the request includes information identifying a second hostname purported to correspond to the first server;
performing a Domain Name System (DNS) lookup using the second hostname, and determining that the second hostname was spoofed by the client device based on a response to the DNS lookup, wherein the response indicates that the first server is not associated with the second hostname; and
in response to determining that the request received from the client device includes the spoofed second hostname, determining that the client device has injected or overridden at least one of an HTTP Host header and a Server Name Indicator in the request, and determining an action to take with respect to the client device.
16. The method of claim 15 further comprising determining that the client device has been compromised.
17. The method of claim 16 wherein the compromise includes mimicking a connection to a trusted service to evade at least one of a decryption and an inspection.
18. The method of claim 16 wherein the compromise includes concealing a connection to a command and control channel.
19. The method of claim 15 wherein the second hostname is included by the client device in an HTTP Host header of a client GET request.
20. The method of claim 15 wherein the second hostname is included by the client device in a Server Name Indicator in a TLS client hello.
21. The method of claim 15 wherein performing the DNS lookup includes querying a cache.
22. The method of claim 15 wherein determining that the second hostname was spoofed by the client device includes comparing a result of the DNS lookup to a destination IP address of a session between the client device and the first server.
23. The method of claim 15 wherein the DNS lookup is performed out of band from the client device establishing the session with the first server.
24. The method of claim 15 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, the client device is prevented from accessing the first server.
25. The method of claim 24 wherein the client device is prevented from accessing the first server by resetting an established session between the client device and the first server.
26. The method of claim 15 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, an alert is generated.
27. The method of claim 15 wherein, in response to determining that the request received from the client device includes the spoofed second hostname, a log entry is generated.
28. The method of claim 15 further comprising caching a result of the DNS lookup.
29. A computer program product embodied in a tangible non-transitory computer readable storage medium and comprising computer instructions for:
receiving, from a client device, a request to establish a session with a first server, wherein the first server is associated with a first hostname, and wherein the request includes information identifying a second hostname purported to correspond to the first server;
performing a Domain Name System (DNS) lookup using the second hostname, and determining that the second hostname was spoofed by the client device based on a response to the DNS lookup, wherein the response indicates that the first server is not associated with the second hostname; and
in response to determining that the request received from the client device includes the spoofed second hostname, determining that the client device has injected or overridden at least one of an HTTP Host header and a Server Name Indicator in the request, and determining an action to take with respect to the client device.