CVE-2007-4205
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 · uneditedXHA (Linux-HA) on the BlueCat Networks Adonis DNS/DHCP Appliance 5.0.2.8 allows remote attackers to cause a denial of service (heartbeat control process crash) via a UDP packet to port 694. NOTE: this may be the same as CVE-2006-3121.
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 confidenceThe XHA (Linux-HA) heartbeat service on BlueCat Adonis DNS/DHCP Appliance 5.0.2.8 contains a vulnerability where processing a specially crafted UDP packet on port 694 causes the heartbeat control process to crash, resulting in a denial of service condition.
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<= 1.2.4CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Linux-HA Heartbeat is installedLook for the heartbeat package using the system package manager (rpm -qa | grep heartbeat, dpkg -l | grep heartbeat, or ls /usr/lib/heartbeat/) and check for running processes (ps aux | grep heartbeat)Affected if No heartbeat package or process is found - the system is not running the affected software
-
Determine the Heartbeat versionQuery the installed package version (rpm -q heartbeat, dpkg -s heartbeat) or check version files in /usr/lib/heartbeat/ or /etc/ha.d/Affected if The installed version is 1.2.4 or lower
-
Verify port 694 UDP is listeningUse netstat (netstat -ulnp | grep 694) or ss (ss -ulnp | grep 694) to check if port 694 is open and listening for UDP trafficAffected if Port 694 UDP is not listening - the vulnerable service is not exposed
-
Check network exposure of the heartbeat serviceReview firewall rules (iptables -L, ufw status) and network configuration to determine if port 694 UDP is accessible from network segments outside the trusted cluster nodesAffected if Port 694 UDP is blocked by firewall or only accessible from authorized cluster IP addresses - the vulnerability is not remotely exploitable
A system is affected if it runs Linux-HA Heartbeat version 1.2.4 or lower with UDP port 694 exposed to untrusted networks, allowing remote attackers to send specially crafted packets that crash the heartbeat process.
Generated from the published advisory. Verify against your own configuration.
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 dataRestrict network access to port 694 so only authorized cluster nodes can send heartbeat traffic; implement firewall rules or network segmentation to prevent unauthorized remote attackers from reaching the service.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-4205 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-4205 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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