CVE-2008-0330
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 · uneditedOpen System Consultants (OSC) Radiator before 4.0 allows remote attackers to cause a denial of service (daemon crash) via malformed RADIUS requests, as demonstrated by packets sent by nmap.
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 · high confidenceOpen System Consultants Radiator RADIUS server versions before 4.0 contain a vulnerability in packet handling that allows remote attackers to send malformed RADIUS requests (such as those generated by nmap) and cause the daemon to crash, resulting in denial of service.
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<= 3.17.1CVSS 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
- Complete
AV:N/AC:L/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.
-
Verify Radiator RADIUS server is installedCheck for Radiator installation directories (typically /usr/local/radiator, /opt/radiator, or the perl Radiator distribution), or search for radiator.exe, Radiator.cfg, or similar Radiator-specific files on the system. Also check running processes for 'radiator' or 'radiusd' processes.Affected if Radiator RADIUS server software is found on the system
-
Determine the installed Radiator versionRun 'perl -MRadiator -e "print $Radiator::VERSION"' if Radiator perl modules are installed, or check the version string in the Radiator installation directory files, release notes, or the software inventory if managed by a package manager.Affected if The installed version is 3.17.1 or any version lower than 3.17.1 (versions before 4.0 are affected)
-
Confirm the RADIUS service is runningCheck if the Radiator daemon is actively running using process listing commands (ps aux | grep radiator, tasklist on Windows, or systemctl status radiator) and verify it is listening on RADIUS ports 1645/1812 (authentication) and optionally 1646/1813 (accounting).Affected if The Radiator RADIUS service is running and actively listening for RADIUS requests
-
Assess network exposure of RADIUS portsVerify that UDP ports 1645/1812 (and 1646/1813 if accounting is enabled) are accessible from untrusted networks by reviewing firewall rules, listening sockets (netstat -ulnp | grep -E '1645|1812'), or performing a port scan from an external perspective.Affected if RADIUS ports are exposed to network segments that contain untrusted or attacker-accessible systems, enabling remote malformed packet delivery
You are affected if Radiator RADIUS server version 3.17.1 or lower is installed and the RADIUS service is running with accessible network ports, allowing remote attackers to send malformed packets that can crash the daemon.
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 dataUpgrade to Radiator version 4.0 or later to obtain the fix for malformed packet handling. Additionally, consider network segmentation and firewall rules to limit RADIUS access to trusted authentication servers only.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0330 — 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-2008-0330 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