Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2001-1081: Format string vulnerabilities in Livingston/Lucent RADIUS before 2.1.va.1 may allow local or remote attackers

48
This month
HIGH 7.5DOWNGRADEDOWNGRADE

CVE-2001-1081 is a high-severity flaw (CVSS 7.5) affecting radius, radius. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 into log messages.

Why this priority

  • High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
EPSS exploit chance2.8% (top 14%)
CISA exploited listNo
Published2001-07-06
Last modified2026-06-16
Publisher (CNA): MITRE · Vendor: lucent · simon horms

Share: LinkedIn · X · Reddit

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

lucent radius DOWNGRADE
Affected: 2.1.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1.2
1. Check installed version
apt-cache policy radius || rpm -q radius || radius --version
2. No fixed release: DOWNGRADE to a release before 2.1.2 (Debian / Ubuntu)
apt-cache madison radius sudo apt install radius=<VERSION_BEFORE_2.1.2> sudo apt-mark hold radius
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list radius sudo dnf downgrade radius-<VERSION_BEFORE_2.1.2> sudo dnf versionlock add radius
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
simon horms radius DOWNGRADE
Affected: 2.1_2
Fixed in: no fixed release known
Safe to downgrade to: a release before 2.1_2
1. Check installed version
apt-cache policy radius || rpm -q radius || radius --version
2. No fixed release: DOWNGRADE to a release before 2.1_2 (Debian / Ubuntu)
apt-cache madison radius sudo apt install radius=<VERSION_BEFORE_2.1_2> sudo apt-mark hold radius
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list radius sudo dnf downgrade radius-<VERSION_BEFORE_2.1_2> sudo dnf versionlock add radius
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2001-1081?

radius: downgrade or apply the listed mitigation; radius: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2001-1081 being exploited?

CVE-2001-1081 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2001-1081 affect?

CVE-2001-1081 affects radius, radius. Severity is high (CVSS 7.5). 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 into log messages.

How urgent is CVE-2001-1081?

Priority 48/100. High severity

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.