CVE-2005-0877: High severity Dnsmasq Dnsmasq vulnerability
Published 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.
Affected Software
22 affected components
Dnsmasq Dnsmasq=2.14
Dnsmasq Dnsmasq=2.0
Dnsmasq Dnsmasq=2.6
Dnsmasq Dnsmasq=2.19
Dnsmasq Dnsmasq=2.12
Dnsmasq Dnsmasq=2.3
Dnsmasq Dnsmasq=2.8
Dnsmasq Dnsmasq=2.17
Dnsmasq Dnsmasq=2.5
Dnsmasq Dnsmasq=2.9
Dnsmasq Dnsmasq=2.18
Dnsmasq Dnsmasq=2.20
Dnsmasq Dnsmasq=2.11
Dnsmasq Dnsmasq=2.7
Dnsmasq Dnsmasq=2.16
Dnsmasq Dnsmasq=2.15
Dnsmasq Dnsmasq=2.2
Dnsmasq Dnsmasq=2.1
Dnsmasq Dnsmasq=2.4
Dnsmasq Dnsmasq=2.13
Dnsmasq Dnsmasq=2.10
thekelleys dnsmasq<2.21
Remediation
Patch Available
Patch Available
Event History
Mar 26, 2005
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Frequently Asked Questions
1
What is the severity of CVE-2005-0877?
CVE-2005-0877 is considered a medium-level vulnerability as it allows remote attackers to poison the DNS cache.
2
How do I fix CVE-2005-0877?
You can fix CVE-2005-0877 by upgrading Dnsmasq to version 2.21 or later.
3
What versions of Dnsmasq are affected by CVE-2005-0877?
CVE-2005-0877 impacts all Dnsmasq versions prior to 2.21.
4
What are the potential impacts of CVE-2005-0877?
The potential impacts of CVE-2005-0877 include DNS cache poisoning, which can lead to users being directed to malicious sites.
5
Is there a workaround for CVE-2005-0877 if I cannot upgrade Dnsmasq?
If upgrading is not possible, you may configure Dnsmasq to minimize the attack surface by limiting source IPs and implementing upstream DNS security.