First published: Sat Mar 26 2005(Updated: )
Dnsmasq before 2.21 allows remote attackers to poison the DNS cache via answers to queries that were not made by Dnsmasq.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
thekelleys Dnsmasq | =2.0 | |
thekelleys Dnsmasq | =2.1 | |
thekelleys Dnsmasq | =2.2 | |
thekelleys Dnsmasq | =2.3 | |
thekelleys Dnsmasq | =2.4 | |
thekelleys Dnsmasq | =2.5 | |
thekelleys Dnsmasq | =2.6 | |
thekelleys Dnsmasq | =2.7 | |
thekelleys Dnsmasq | =2.8 | |
thekelleys Dnsmasq | =2.9 | |
thekelleys Dnsmasq | =2.10 | |
thekelleys Dnsmasq | =2.11 | |
thekelleys Dnsmasq | =2.12 | |
thekelleys Dnsmasq | =2.13 | |
thekelleys Dnsmasq | =2.14 | |
thekelleys Dnsmasq | =2.15 | |
thekelleys Dnsmasq | =2.16 | |
thekelleys Dnsmasq | =2.17 | |
thekelleys Dnsmasq | =2.18 | |
thekelleys Dnsmasq | =2.19 | |
thekelleys Dnsmasq | =2.20 | |
the kelleys dnsmasq | <2.21 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2005-0877 is considered a medium-level vulnerability as it allows remote attackers to poison the DNS cache.
You can fix CVE-2005-0877 by upgrading Dnsmasq to version 2.21 or later.
CVE-2005-0877 impacts all Dnsmasq versions prior to 2.21.
The potential impacts of CVE-2005-0877 include DNS cache poisoning, which can lead to users being directed to malicious sites.
If upgrading is not possible, you may configure Dnsmasq to minimize the attack surface by limiting source IPs and implementing upstream DNS security.