cve.bz

CVE-2022-30256 (Phoenix Domain) maradns maradns

7.5 highEPSS 1.2%

Known as Phoenix Domain

High (7.5) in maradns maradns. EPSS 1.2% estimated probability of exploitation activity in the next 30 days.

On this page
An issue was discovered in MaraDNS Deadwood through 3.5.0021 that allows variant V1 of unintended domain name resolution. A revoked domain name can still be resolvable for a long time, including expired domains and taken-down malicious domains. The effects of an exploit would be widespread and highly impactful, because the exploitation conforms to de facto DNS specifications and operational practices, and overcomes current mitigation patches for "Ghost" domain names.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
1.2% (up from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2025-04-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-672 Operation on a Resource after Expiration or Release
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-30256 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-30256?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-30256?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-30256 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
maradns:maradnsbefore 3.4.03
maradns:maradnsfrom 3.5.0 before 3.5.0022

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian10maradns2.0.13-1.2+deb10u1DLA-3457-1
Debian11maradns2.0.13-1.4+deb11u1DEBIAN-CVE-2022-30256 DSA-5441-1
Ubuntu20.04:LTSmaradns2.0.13-1.4+deb11u1build0.20.04.1UBUNTU-CVE-2022-30256 USN-6271-1
Ubuntu22.04:LTSmaradns2.0.13-1.4+deb11u1build0.22.04.1UBUNTU-CVE-2022-30256 USN-6271-1
UbuntuPro:16.04:LTSmaradns2.0.13-1ubuntu0.1~esm1UBUNTU-CVE-2022-30256 USN-6271-1
UbuntuPro:18.04:LTSmaradns2.0.13-1.2ubuntu0.1~esm1UBUNTU-CVE-2022-30256 USN-6271-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

References

Check your stackJSON