What is the severity of CVE-2008-1637?

CVE-2008-1637 has a medium severity rating due to potential DNS cache poisoning vulnerabilities.

How do I fix CVE-2008-1637?

To mitigate CVE-2008-1637, upgrade PowerDNS Recursor to version 3.1.5 or later.

What is the impact of exploiting CVE-2008-1637?

Exploiting CVE-2008-1637 allows attackers to poison the DNS cache, leading to the redirection of users to malicious sites.

Which versions of PowerDNS are affected by CVE-2008-1637?

CVE-2008-1637 affects PowerDNS Recursor versions prior to 3.1.5.

What causes the vulnerability in CVE-2008-1637?

CVE-2008-1637 is caused by insufficient randomness in TRXID values and UDP source port numbers utilized by PowerDNS.

Vulnerability/
CVE-2008-1637

medium

6.8

CWE

189

2/4/2008

7/8/2024

CVE-2008-1637

First published: Wed Apr 02 2008(Updated: )

PowerDNS Recursor before 3.1.5 uses insufficient randomness to calculate (1) TRXID values and (2) UDP source port numbers, which makes it easier for remote attackers to poison a DNS cache, related to (a) algorithmic deficiencies in rand and random functions in external libraries, (b) use of a 32-bit seed value, and (c) choice of the time of day as the sole seeding information.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
PowerDNS	<=3.1.4

Remedy

http://doc.powerdns.com/powerdns-advisory-2008-01.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2008-1637?
CVE-2008-1637 has a medium severity rating due to potential DNS cache poisoning vulnerabilities.
How do I fix CVE-2008-1637?
To mitigate CVE-2008-1637, upgrade PowerDNS Recursor to version 3.1.5 or later.
What is the impact of exploiting CVE-2008-1637?
Exploiting CVE-2008-1637 allows attackers to poison the DNS cache, leading to the redirection of users to malicious sites.
Which versions of PowerDNS are affected by CVE-2008-1637?
CVE-2008-1637 affects PowerDNS Recursor versions prior to 3.1.5.
What causes the vulnerability in CVE-2008-1637?
CVE-2008-1637 is caused by insufficient randomness in TRXID values and UDP source port numbers utilized by PowerDNS.

agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/severity
agent/weakness
agent/remedy
agent/last-modified-date
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
collector/nvd-historical
vendor/powerdns
canonical/powerdns
version/powerdns/3.1.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2008-1637?
CVE-2008-1637 has a medium severity rating due to potential DNS cache poisoning vulnerabilities.
How do I fix CVE-2008-1637?
To mitigate CVE-2008-1637, upgrade PowerDNS Recursor to version 3.1.5 or later.
What is the impact of exploiting CVE-2008-1637?
Exploiting CVE-2008-1637 allows attackers to poison the DNS cache, leading to the redirection of users to malicious sites.
Which versions of PowerDNS are affected by CVE-2008-1637?
CVE-2008-1637 affects PowerDNS Recursor versions prior to 3.1.5.
What causes the vulnerability in CVE-2008-1637?
CVE-2008-1637 is caused by insufficient randomness in TRXID values and UDP source port numbers utilized by PowerDNS.