A security issue and two vulnerabilities have been reported in djbdns, which can be exploited by malicious people to conduct spoofing attacks or manipulate certain data.
1) A security issue is caused due to the dnscache server component improperly handling SOA (Start of Authority) records. This can be exploited to increase the chances for a successful DNS poisoning attack by continuously sending a large number of SOA requests and spoofed replies.
2) An error exists in tinydns and axfrdns when processing name compression encoding schemes to produce response packets. This can be exploited to return arbitrary DNS records outside of the specified zone in responses to queries for the controlled domain.
Successful exploitation of this vulnerability requires pulling records from a malicious DNS server.
The security issue and the vulnerabilities are reported in version 1.05. Other versions may also be affected.
Solution: Although no effective workaround exists, attempted blocking of SOA requests from untrusted sources may mitigate exploitation. Do not pull records from untrusted servers. Clear the DNS cache periodically or enable DNSSEC.
Provided and/or discovered by: 1) Kevin Day
2) Matthew Dempsky
3) Reported via the "Ghost Domain Names" presentation at the NDSS conference.
Original Advisory: 1) http://www.your.org/dnscache/
Do you have additional information related to this advisory?
Please provide information about patches, mitigating factors, new versions, exploits, faulty patches, links, and other relevant data by posting comments to this Advisory. You can also send this
information to email@example.com
Subject: djbdns DNS Cache Poisoning and DNS Record Manipulation
No posts yet
You must be logged in to post a comment.
Secunia Customer Login
Not a customer already?
Learn more about how our market leading Vulnerability Management solutions can help you manage risk and ensure compliance.