Research

More on DNS Poisoning

We’ve had a few queries from readers asking what DNS poisoning actually is.
As stated yesterday, DNS poisoning is the manipulation of an IP address for a certain DNS entry

So what does that really mean? To fully understand this, first you need to know some basics about how addresses work.

There are a few very big DNS servers which provide other, smaller, DNS servers with DNS/I.P. entries. These entries get stored in the cache of the smaller DNS servers. It’s not the big servers, but the smaller ones that are being poisoned. Poisoning only lasts until the DNS server rechecks the entries with a large DNS server, so you may also hear this called DNS cache poisoning.

So, if you enter www.kaspersky.com in your browser, the DNS server is queried for the IP address assigned to this DNS name. (DNS names are mainly to make our lives easier). In this case the DNS server will respond with the IP address 81.176.69.70.

So the goal of DNS poisoning is to make the (small) DNS server say that another IP address (one of a site containing malicious content) is assigned to a certain DNS name.

How exactly can servers be poisoned? Well, DNS servers need to run an operating system and software to perform their tasks. Insecure settings and/or vulnerabilities in either of these can lead to the DNS server being poisoned, usually by malformed packets being sent to the server.

How can you protect yourself? This is a tricky question, because as a (DNS) client there is not that much you can do. For example, with modified hosts files, it’s a local issue. But in this case the issue isn’t local – it’s up to your ISP or system administrator to make sure that everything is secure.

When DNS servers are poisoned so that users are directed to clones of legitimate sites, if the poisoning is done correctly, and the cloned sites are carefully constructed, the user won’t notice anything unusual.

And I for one don’t know many people who know the real IP addresses of the sites they visit…

More on DNS Poisoning

Your email address will not be published. Required fields are marked *

 

Reports

Lazarus targets defense industry with ThreatNeedle

In mid-2020, we realized that Lazarus was launching attacks on the defense industry using the ThreatNeedle cluster, an advanced malware cluster of Manuscrypt (a.k.a. NukeSped). While investigating this activity, we were able to observe the complete life cycle of an attack, uncovering more technical details and links to the group’s other campaigns.

Sunburst backdoor – code overlaps with Kazuar

While looking at the Sunburst backdoor, we discovered several features that overlap with a previously identified backdoor known as Kazuar. Our observations shows that Kazuar was used together with Turla tools during multiple breaches in past years.

Lazarus covets COVID-19-related intelligence

As the COVID-19 crisis grinds on, some threat actors are trying to speed up vaccine development by any means available. We have found evidence that the Lazarus group is going after intelligence that could help these efforts by attacking entities related to COVID-19 research.

Sunburst: connecting the dots in the DNS requests

We matched private and public DNS data for the SUNBURST-malware root C2 domain with the CNAME records, to identify who was targeted for further exploitation. In total, we analyzed 1722 DNS records, leading to 1026 unique target name parts and 964 unique UIDs.

Subscribe to our weekly e-mails

The hottest research right in your inbox