CVE-2012-1570: Medium severity MaraDNS MaraDNS vulnerability

Published Mar 19, 2012
·
Updated

It was reported [1],[2] that MaraDNS suffers from a flaw where it is susceptible to spoofing attacks. Due to an error in the cache update policy, which does not properly handle revoked domain names, a remote attacker could keep a domain name resolvable after it has been deleted from the registration.

This flaw is fixed in versions 1.3.0.7.15 and 1.4.12, and is reported to affect all prior versions.

[1] http://www.maradns.org/changelog.html [2] https://secunia.com/advisories/48492/

Other sources

The resolver in MaraDNS before 1.3.0.7.15 and 1.4.x before 1.4.12 overwrites cached server names and TTL values in NS records during the processing of a response to an A record query, which allows remote attackers to trigger continued resolvability of revoked domain names via a "ghost domain names" attack.

Affected Software

2 affected components
MaraDNS MaraDNS<1.3.07.15
MaraDNS MaraDNS>=1.4.0<1.4.12

Event History

Mar 19, 2012
Data Sourced
06:34 PM
DescriptionSeverityAffected Software
Mar 28, 2012
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2012-1570?

CVE-2012-1570 is classified as a moderate severity vulnerability due to its potential for spoofing attacks.

2

How does CVE-2012-1570 affect MaraDNS?

CVE-2012-1570 affects MaraDNS by allowing remote attackers to keep a domain name resolvable after it has been revoked.

3

How do I fix CVE-2012-1570?

To fix CVE-2012-1570, it is recommended to upgrade to MaraDNS versions later than 1.4.12 or to patch the software as prompted by vendor recommendations.

4

What versions of MaraDNS are affected by CVE-2012-1570?

CVE-2012-1570 affects MaraDNS versions prior to 1.3.07.15 and versions within the range of 1.4.0 to 1.4.12 inclusive.

5

Is it possible to mitigate CVE-2012-1570 without upgrading?

Mitigating CVE-2012-1570 without upgrading may involve configuring DNS settings to prevent the caching of revoked domain names, although this may not be completely effective.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203