Researchers from Ruhr-Universit\u00e4t Bochum & New York University Abu Dhabi have uncovered a new attack against devices using the Long-Term Evolution (LTE) network protocol. LTE, which is a form of 4G, is a mobile communications standard used by billions of devices and the largest cellular providers around the world.\nIn other words, the attack can be used against you.\nThe research team has named the attack \u201caLTEr\u201d and it allows the attacker to intercept communications using a man-in-the-middle technique and redirect the victim to malicious websites using DNS spoofing.\nNote: According to their FAQ question: "Is there a logo for the attacks", the answer is: "Maybe. There are no stickers, t-shirts, songs, ...". You gotta love their sense of humor since no attack is truly relevant without its own logo! \u263b\nThe aLTEr attack\nThis attack works by taking advantage of a design flaw within the LTE network \u2014 the data link layer (aka: layer-2) of the LTE network is encrypted with AES-CTR but it is not integrity-protected, which is why an attacker can modify the payload.\nAs a result, the attacker is performing a classic man-in-the-middle where they are posing as a cell tower to the victim, while pretending to be the real subscriber to the real network. The traffic from the victim is sent to the attacker where it is modified and forwarded into the real network.\n Aaron Woland\n\nFigure 1 \u2013 the aLTEr MiTM attack\n\n\nThese types of attacks are not only limited to LTE networks. 5G networks may also be vulnerable to these attacks in future \u2013 if they don\u2019t institute integrity protection.\nProtecting against these types of attacks?\nDNS is foundational to how the internet works; before any app connects to its service, before any web browser connects to the web site, before any email is sent: a DNS lookup is performed. Traditional DNS is designed to be very quick, not secure.\nDNS spoofing attacks can be prevented by adding security to DNS itself, leveraging encryption and intelligent policies for name resolution. One example of this is implementing RFC 7858 or RFC 8310. These RFC\u2019s reference the use of DNS over Transport Layer Security (TLS) and DNS over Datagram TLS (DTLS).\nDNS over TLS or DTLS will protect devices from the aLTEr attack, by providing encryption of the DNS traffic that includes integrity-protection. There have been articles on Google Android\u2019s O release (aka: Oreo) enabling DNS over TLS out of the box, by default. This helps when the DNS servers the device is connecting to are leveraging DNS over TLS; but naturally, the DNS servers do get assigned by the network the device is connected to. \u00a0Cloudflare\u2019s DNS service does over DNS over HTTPS already, but not many clients are able to leverage it just yet.\nSince this is my blog, I guess I\u2019m entitled to share my opinion. From the testing results that I have seen, DNS over TLS has a bit too much overhead and is lacking the performance required by DNS. This is why DNS over DTLS makes more a little more sense to me. We saw this with \u201cSSL VPN\u201d (which is a misnomer, it\u2019s actually a TLS VPN), and time sensitive traffic for voice over IP. Moving the VPN to DTLS instead of TLS increased the performance and made VoIP with VPN truly achievable.\nAnother possible solution would be to leverage DNS over HTTPS, which does interest a lot of people, especially those who may have malicious intentions, where the DNS requests from the app itself (most likely a Tor client or a browser) would be sent directly to a DNS server, leveraging an HTTPS communication. This is mostly theoretical at this juncture, as not many services enable DNS over HTTPS.\u00a0 Google DNS does enable this communication type, as does Cloudflare\u2019s DNS service. However, not many (if any) clients or apps are built to leverage the service yet. Additionally, since HTTPS is leveraging TLS this would add the overhead of the TLS session, also.\nDNSCrypt and the Cisco Security Connector for iOS\nThere is another, older option, which has successfully been implemented for quite some time already, known as DNSCrypt. Cisco Umbrella (the solution formerly known as OpenDNS) has been using DNSCrypt to secure DNS for many years.\nAlong these lines, Apple and Cisco have partnered to deliver the deepest level of visibility and control for enterprise-owned iOS devices with the Cisco Security Connector (CSC) for iOS. [Disclamer: the author is a principal engineer for Cisco.]\nCSC for iOS protects users from connecting to malicious sites, leveraging DNS as a control plane. The protections occur whether on the corporate network, on public Wi-Fi, or on cellular network. CSC encrypts the DNS queries and sends them to Cisco\u2019s Umbrella service for resolution, which protects your user population from connecting to nefarious web sites and prevents the DNS spoofing attacks.