CVE-2017-9148: The 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…
Noroxi assessment
Priority: Plan (action score 40/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: 3.9% (FIRST EPSS); higher than 90.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 (Debian:12) 3.0.12+dfsg-5; freeradius (Debian:7) 2.1.12+dfsg-1.2+deb7u1; freeradius-server (openSUSE:Tumbleweed) 3.0.23-1.5.
Add it to your regular patch cycle. Upgrade to freeradius (Debian:12) 3.0.12+dfsg-5; freeradius (Debian:7) 2.1.12+dfsg-1.2+deb7u1; freeradius-server (openSUSE:Tumbleweed) 3.0.23-1.5 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
Primary sources: NVD · CVE.org · FIRST EPSS
The 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 reliably prevent resumption of an unauthenticated session, which allows remote attackers (such as malicious 802.1X supplicants) to bypass authentication via PEAP or TTLS.
- Published
- May 29, 2017
- Updated
- Jun 16, 2026
- EPSS
- 3.9% · 90th percentile
- CWE
- CWE-287
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.9%
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.
Is your version affected? Check itNoroxi 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 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- freeradius freeradius2.1.1
- freeradius freeradius2.1.2
- freeradius freeradius2.1.3
- freeradius freeradius2.1.4
- freeradius freeradius2.1.6
- freeradius freeradius2.1.7
- freeradius freeradius3.0.0
- freeradius freeradius3.0.1
+12 more rows
- freeradius freeradius3.0.2
- freeradius freeradius3.0.3
- freeradius freeradius3.0.4
- freeradius freeradius3.0.5
- freeradius freeradius3.0.6
- freeradius freeradius3.0.7
- freeradius freeradius3.0.8
- freeradius freeradius3.0.9
- freeradius freeradius3.1.0
- freeradius freeradius3.1.1
- freeradius freeradius3.1.2
- freeradius freeradius3.1.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | freeradius | before 3.0.12+dfsg-5 | 3.0.12+dfsg-5 |
| Debian:7 | freeradius | before 2.1.12+dfsg-1.2+deb7u1 | 2.1.12+dfsg-1.2+deb7u1 |
| 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.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-debuginfo | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-devel | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-doc | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-krb5 | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-ldap | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-mysql | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-perl | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-postgresql | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-python | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-sqlite | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-unixODBC | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| Red Hat:enterprise_linux:7::server | freeradius-utils | before 0:3.0.4-8.el7_3 | 0:3.0.4-8.el7_3 |
| SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | freeradius-server | before 3.0.3-17.4.1 | 3.0.3-17.4.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | freeradius-server | before 2.1.1-7.24.1 | 2.1.1-7.24.1 |
Same product
freeradius: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11234FreeRADIUS before 3.0.19 does not prevent use of reflection for authentication spoofing, aka a "Dragonblood" issue, a similar issue to…41Plan
- 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…41Plan
- 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…41Plan
Published before and after this one in the same product
- ← EarlierCVE-2015-8764Mar 27, 2017 · Off-by-one error in the EAP-PWD module in FreeRADIUS 3.0 through 3.0.8, which triggers a buffer overflow.32Monitor
- ← EarlierCVE-2015-4680Apr 5, 2017 · FreeRADIUS 2.2.x before 2.2.8 and 3.0.x before 3.0.9 does not properly check revocation of intermediate CA certificates.31Monitor
- Later →CVE-2017-10978Jul 17, 2017 · An FR-GV-201 issue in FreeRADIUS 2.x before 2.2.10 and 3.x before 3.0.15 allows "Read / write overflow in make_secret()" and a denial of…31Monitor
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 |
|---|---|---|
| debian:freeradius | 3.0.12+dfsg-5 · Debian:12 | Package registry (OSV) |
| opensuse:freeradius-server | 3.0.23-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:freeradius | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-debuginfo | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-devel | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-doc | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-krb5 | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-ldap | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-mysql | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-perl | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-postgresql | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-python | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-sqlite | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:freeradius-unixODBC | 0:3.0.4-8.el7_3 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:freeradius-server | 3.0.3-17.4.1 · SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
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 middleware
app.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 (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.