Radius vulnerabilitiesRanked by how likely they are to be used.

Product4 versions
The short answer

Radius is made by Lucent. We track 5 published vulnerabilities in it, across 4 versions. None of them is on the list of flaws known to be exploited today. If you run Radius, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Radius vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Radius's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Radius flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 8.5%

    Buffer overflow in digest calculation function of multiple RADIUS implementations allows remote attackers to cause a denial of service and possibly execute arbitrary code via shared secret data.

    CVSS7.5Published4 Mar 2002
  2. 6.7%

    Multiple buffer overflows in RADIUS daemon radiusd in (1) Merit 3.6b and (2) Lucent 2.1-2 RADIUS allow remote attackers to cause a denial of service or execute arbitrary commands.

    CVSS10.0Published21 Jul 2001
  3. 5.4%

    Multiple RADIUS implementations do not properly validate the Vendor-Length of the Vendor-Specific attribute, which allows remote attackers to cause a denial of service (crash) via a Vendor-Length that is less than 2.

    CVSS5.0Published4 Mar 2002
  4. 2.8%

    Format string vulnerabilities in Livingston/Lucent RADIUS before 2.1.va.1 may allow local or remote attackers to cause a denial of service and possibly execute arbitrary code via format specifiers that are injected...

    CVSS7.5Published6 Jul 2001
  5. 1.4%

    Directory traversal vulnerability in Livingston/Lucent RADIUS before 2.1.va.1 may allow attackers to read arbitrary files via a ..

    CVSS5.0Published13 Jul 2001
EdgeProtect

Running Radius? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 5 published vulnerabilities listed under the name Radius, across 4 versions.

None of Radius's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Radius. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.