2020
DOI: 10.48550/arxiv.2012.07432
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Cross Layer Attacks and How to Use Them (for DNS Cache Poisoning, Device Tracking and More)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
6
0

Year Published

2021
2021
2022
2022

Publication Types

Select...
4

Relationship

0
4

Authors

Journals

citations
Cited by 4 publications
(6 citation statements)
references
References 0 publications
0
6
0
Order By: Relevance
“…In this attacker model, we assume an off-path attacker without any additional capabilities. As demonstrated in a recent study, this attacker can implement a cache poisoning attack on Linux-based DNS revolvers [25]). This attack exploits a vulnerability within the pseudorandom number generator (PRNG) of the Linux operating system (as well as Android) to overcome source port randomization.…”
Section: Off-path Attacker (Op)mentioning
confidence: 98%
See 1 more Smart Citation
“…In this attacker model, we assume an off-path attacker without any additional capabilities. As demonstrated in a recent study, this attacker can implement a cache poisoning attack on Linux-based DNS revolvers [25]). This attack exploits a vulnerability within the pseudorandom number generator (PRNG) of the Linux operating system (as well as Android) to overcome source port randomization.…”
Section: Off-path Attacker (Op)mentioning
confidence: 98%
“…Based on a previous threat analysis of the DNS [10] and recently published DNS cache poisoning attacks [20,25,29], we consider three type of attackers that can acquire the abovementioned capabilities: a man-in-the-middle attacker, an off-path attacker with IP spoofing capability that controls an adjacent machine, and an off-path attacker without any additional capabilities.…”
Section: Threat Modelmentioning
confidence: 99%
“…[57] showed how to use ICMP errors to infer the UDP source ports selected by DNS resolvers. Recently [52] showed how to use side channels to predict the ports due to vulnerable PRNG in Linux kernel. In 2013 [38] provided the first feasibility result for launching cache poisoning by exploiting IPv4 fragmentation.…”
Section: History Of Dns Cache Poisoningmentioning
confidence: 99%
“…For the evaluations in this work we selected three generic cache poisoning methodologies developed in [21,38,57], which are not specific to implementation or setup and do not result due to bugs in randomness generation, such as [52]. We perform Internet-wide measurements of these methodologies testing experimentally DNS cache poisoning against DNS resolution platforms.…”
Section: History Of Dns Cache Poisoningmentioning
confidence: 99%
“…A followup work demonstrated effectiveness of such cache poisoning attacks also against stub resolvers [2]. Side channels were also used to predict the ports due to vulnerable PRNG in Linux kernel [23], these are however difficult to apply in practice. [26] developed a method to leverage ICMP errors to infer the UDP source ports selected by DNS resolvers.…”
Section: Dns Cache Poisoning Chroniclementioning
confidence: 99%