2022
DOI: 10.1109/access.2022.3175497
|View full text |Cite
|
Sign up to set email alerts
|

Summary of DNS Over HTTPS Abuse

Abstract: The Internet Engineering Task Force adopted the DNS over HTTPS protocol in 2018 to remediate privacy issues regarding the plain text transmission of the DNS protocol. According to our observations and the analysis described in this paper, protecting DNS queries using HTTPS entails security threats. This paper surveys DoH related research works and analyzes malicious and unwanted activities that leverage DNS over HTTPS and can be currently observed in the wild. Additionally, we describe three realworld abuse sc… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

2022
2022
2024
2024

Publication Types

Select...
5
4
1

Relationship

0
10

Authors

Journals

citations
Cited by 21 publications
(5 citation statements)
references
References 49 publications
0
5
0
Order By: Relevance
“…All dashboards in graphs appear once the links [47–52] are clicked. Readers are advised to examine the details about the information on each graph.…”
Section: Resultsmentioning
confidence: 99%
“…All dashboards in graphs appear once the links [47–52] are clicked. Readers are advised to examine the details about the information on each graph.…”
Section: Resultsmentioning
confidence: 99%
“…There have been more efforts made by different researchers to utilize the properties and statistical features of the traffic flow to classify DNS-over-HTTPS (DoH) and DoH-based C2 tunnels using machine learning and deep learning models. Notwithstanding previous research on HTTPS traffic analysis, the malware use of HTTPS, or TLS with machine learning using flow-based features [40][41][42][43][44][45], this section focused on studies conducted on DoH traffic and DoH-based tunneling detection using machine learning methods.…”
Section: Dns Tunneling Detection With ML Methodsmentioning
confidence: 99%
“…To do so, DoH encrypts all DNS requests/responses before dispatch via HTTPs protocol. It also uses the same standard HTTPS port number (i.e., port number 443) to encapsulate the DNS request in the HTTPS traffic request [ 36 ]. Despite all such security mechanisms implemented into the DoH protocol, attackers can still use advanced attack approaches to steal information on the fly through the transmission of malicious DoH traffic.…”
Section: Doh Identification Architecturementioning
confidence: 99%