FreeRADIUS before 3.0.19 does not prevent use of reflection for authentication spoofing, aka a "Dragonblood" issue, a similar issue to CVE-2
Noroxi assessment
Priority: Plan (action score 41/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.6% (FIRST EPSS); higher than 94.4% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: freeradius (Alpine:v3.10) 3.0.19-r0; freeradius (Alpine:v3.6) 3.0.13-r3; freeradius (Alpine:v3.7) 3.0.15-r4.
Add it to your regular patch cycle. Upgrade to freeradius (Alpine:v3.10) 3.0.19-r0; freeradius (Alpine:v3.6) 3.0.13-r3; freeradius (Alpine:v3.7) 3.0.15-r4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
FreeRADIUS before 3.0.19 does not prevent use of reflection for authentication spoofing, aka a "Dragonblood" issue, a similar issue to CVE-2019-9497.
- Published
- Apr 22, 2019
- Updated
- Jun 16, 2026
- EPSS
- 7.6% · 94th percentile
- CWE
- CWE-287
Report tools
Action score
41
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| freeradius | freeradius | cpe:2.3:a:freeradius:freeradius |
| fedoraproject | fedora | cpe:2.3:o:fedoraproject:fedora |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux18.04
- canonical ubuntu linux18.10
- canonical ubuntu linux19.04
- fedoraproject fedoraall versions
- freeradius freeradiusbefore 3.0.19
- redhat enterprise linux7.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | freeradius | before 3.0.19-r0 | 3.0.19-r0 |
| Alpine:v3.6 | freeradius | before 3.0.13-r3 | 3.0.13-r3 |
| Alpine:v3.7 | freeradius | before 3.0.15-r4 | 3.0.15-r4 |
| Alpine:v3.8 | freeradius | before 3.0.17-r3 | 3.0.17-r3 |
| Alpine:v3.9 | freeradius | before 3.0.17-r5 | 3.0.17-r5 |
| Debian:12 | freeradius | before 3.0.17+dfsg-1.1 | 3.0.17+dfsg-1.1 |
| openSUSE:Leap 15.0 | freeradius-server | before 3.0.16-lp150.2.3.1 | 3.0.16-lp150.2.3.1 |
| openSUSE:Leap 15.1 | freeradius-server | before 3.0.16-lp151.4.3.1 | 3.0.16-lp151.4.3.1 |
| openSUSE:Tumbleweed | freeradius-server | before 3.0.23-1.5 | 3.0.23-1.5 |
| Red Hat:enterprise_linux:7::server | freeradius | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-debuginfo | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-devel | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-doc | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-krb5 | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-ldap | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-mysql | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-perl | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-postgresql | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-python | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-sqlite | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-unixODBC | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:7::server | freeradius-utils | before 0:3.0.13-10.el7_6 | 0:3.0.13-10.el7_6 |
| Red Hat:enterprise_linux:8::appstream | freeradius | before 0:3.0.17-4.module+el8.0.0+3108+851cb559 | 0:3.0.17-4.module+el8.0.0+3108+851cb559 |
| Red Hat:enterprise_linux:8::appstream | freeradius-debuginfo | before 0:3.0.17-4.module+el8.0.0+3108+851cb559 | 0:3.0.17-4.module+el8.0.0+3108+851cb559 |
+24
Same product
freeradius: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-10984An FR-GV-301 issue in FreeRADIUS 3.x before 3.0.15 allows "Write overflow in data2vp_wimax()" - this allows remote attackers to cause a deni41Plan
- CVE-2017-10979An FR-GV-202 issue in FreeRADIUS 2.x before 2.2.10 allows "Write overflow in rad_coalesce()" - this allows remote attackers to cause a denia41Plan
- CVE-2003-0968Stack-based buffer overflow in SMB_Logon_Server of the rlm_smb experimental module for FreeRADIUS 0.9.3 and earlier allows remote attackers 41Plan
- CVE-2024-3596RADIUS Protocol under RFC2865 is vulnerable to forgery attacks.40Plan
- CVE-2019-11235FreeRADIUS before 3.0.19 mishandles the "each participant verifies that the received scalar is within a range, and that the received group e40Plan
- CVE-2017-9148The TLS session cache in FreeRADIUS 2.1.1 through 2.1.7, 3.0.x before 3.0.14, 3.1.x before 2017-02-04, and 4.0.x before 2017-02-04 fails to 40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:freeradius | 3.0.19-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:freeradius | 3.0.17+dfsg-1.1 · Debian:12 | Package registry (OSV) |
| opensuse:freeradius-server | 3.0.16-lp150.2.3.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:freeradius | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-debuginfo | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-devel | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-doc | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-krb5 | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-ldap | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-mysql | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-perl | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-postgresql | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-python | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-sqlite | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-unixODBC | 0:3.0.13-10.el7_6 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:freeradius-server | 3.0.3-17.12.1 · SUSE:OpenStack Cloud 7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- lists.opensuse.org/opensuse-security-announce/2019-05/msg00032.html
- lists.opensuse.org/opensuse-security-announce/2020-04/msg00033.html
- access.redhat.com/errata/RHSA-2019:1131
- access.redhat.com/errata/RHSA-2019:1142
- bugzilla.redhat.com/show_bug.cgi?id=1695783
- freeradius.org/release_notes/?br=3.0.x&re=3.0.19
- freeradius.org/security/
- papers.mathyvanhoef.com/dragonblood.pdf
- usn.ubuntu.com/3954-1/
- www.kb.cert.org/vuls/id/871675/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.