dbcve.org
MaradnsApplication

CVE-2008-0061

MEDIUM · 5.0 CVSS v2.0 Published 2008-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
MaraDNS 1.0 before 1.0.41, 1.2 before 1.2.12.08, and 1.3 before 1.3.07.04 allows remote attackers to cause a denial of service via a crafted DNS packet that prevents an authoritative name (CNAME) record from resolving, aka "improper rotation of resource records."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

MaraDNS versions 1.0 before 1.0.41, 1.2 before 1.2.12.08, and 1.3 before 1.3.07.04 contain a denial of service vulnerability where crafted DNS packets prevent authoritative CNAME records from resolving, caused by improper rotation of resource records.

MitigationUpgrade MaraDNS to version 1.0.41, 1.2.12.08, 1.3.07.04 or later. If immediate upgrade is not possible, consider network-level filtering to limit exposure to untrusted DNS queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MaradnsApplication
Affected:= 1.0.00= 1.0.01= 1.0.02= 1.0.03= 1.0.04= 1.0.05= 1.0.06= 1.0.07= 1.0.08= 1.0.09= 1.0.10= 1.0.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify MaraDNS is installed
    Check for MaraDNS process running or executable present (e.g., ps aux | grep maradns, which maradns, or locate maradns)
    Affected if MaraDNS is not found on the system, the system is not affected by this CVE
  2. Determine installed MaraDNS version
    Run 'maradns -v' or 'maradns --version' to obtain the exact version number
    Affected if Version is 1.0.x below 1.0.41, or 1.2.x below 1.2.12.08, or 1.3.x below 1.3.07.04
  3. Check if server is configured as authoritative
    Examine MaraDNS configuration file (typically server.yaml or mararc) for authoritative zone definitions
    Affected if Server is configured as authoritative for any zones and version is in the affected ranges

System is affected if MaraDNS is running with a version in the 1.0.x series before 1.0.41, 1.2.x before 1.2.12.08, or 1.3.x before 1.3.07.04 and is configured as an authoritative DNS server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MaraDNS to version 1.0.41, 1.2.12.08, 1.3.07.04 or later. If immediate upgrade is not possible, consider network-level filtering to limit exposure to untrusted DNS queries.

Fix this in Maradns Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2008-0061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2008-0061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data