CVE-2021-31378

Junos OS: An attacker sending spoofed RADIUS messages to a Junos OS device configured for broadband services may cause broadband subscribers to remain stuck in a "Terminating" state.

HIGH

7.5

CVSS Score

Published: October 19, 2021 at 06:17 PM UTC

Updated: June 17, 2026 at 03:51 AM UTC

1 product affected across 1 vendorJunos

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 1%

Description

In broadband environments, including but not limited to Enhanced Subscriber Management, (CHAP, PPP, DHCP, etc.), on Juniper Networks Junos OS devices where RADIUS servers are configured for managing subscriber access and a subscriber is logged in and then requests to logout, the subscriber may be forced into a "Terminating" state by an attacker who is able to send spoofed messages appearing to originate from trusted RADIUS server(s) destined to the device in response to the subscriber's request. These spoofed messages cause the Junos OS General Authentication Service (authd) daemon to force the broadband subscriber into this "Terminating" state which the subscriber will not recover from thereby causing a Denial of Service (DoS) to the endpoint device. Once in the "Terminating" state, the endpoint subscriber will no longer be able to access the network. Restarting the authd daemon on the Junos OS device will temporarily clear the subscribers out of the "Terminating" state. As long as the attacker continues to send these spoofed packets and subscribers request to be logged out, the subscribers will be returned to the "Terminating" state thereby creating a persistent Denial of Service to the subscriber. An indicator of compromise may be seen by displaying the output of "show subscribers summary". The presence of subscribers in the "Terminating" state may indicate the issue is occurring. This issue affects: Juniper Networks Junos OS 17.3 versions prior to 17.3R3-S12; 17.4 versions prior to 17.4R3-S5; 18.1 versions prior to 18.1R3-S13; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S5; 18.4 versions prior to 18.4R2-S8, 18.4R3-S9; 19.1 versions prior to 19.1R3-S6; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S6, 19.3R3-S3; 19.4 versions prior to 19.4R1-S4, 19.4R1-S4, 19.4R3-S3; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R3-S1; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2. This issue does not affect: Juniper Networks Junos OS 12.3 version 12.3R1 and later versions; 15.1 version 15.1R1 and later versions.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Junos · Juniper Networks

95%

17.3 ≤ v < 17.3R3-S1217.4 ≤ v < 17.4R3-S518.1 ≤ v < 18.1R3-S1318.2 ≤ v < 18.2R3-S818.3 ≤ v < 18.3R3-S518.4 ≤ v < 18.4R2-S8, 18.4R3-S919.1 ≤ v < 19.1R3-S619.2 ≤ v < 19.2R1-S7, 19.2R3-S319.3 ≤ v < 19.3R2-S6, 19.3R3-S319.4 ≤ v < 19.4R1-S4, 19.4R1-S4, 19.4R3-S320.1 ≤ v < 20.1R320.2 ≤ v < 20.2R3-S120.3 ≤ v < 20.3R320.4 ≤ v < 20.4R321.1 ≤ v < 21.1R217.3 17.3 r1 17.3 r1-s1 17.3 r1-s4 17.3 r2 17.3 r2-s1 17.3 r2-s2 17.3 r2-s3 17.3 r2-s4 17.3 r2-s5 17.3 r3 17.3 r3-s1 17.3 r3-s10 17.3 r3-s11 17.3 r3-s2 17.3 r3-s3 17.3 r3-s4 17.3 r3-s5 17.3 r3-s6 17.3 r3-s7 17.3 r3-s8 17.3 r3-s9 17.4 17.4 r1 17.4 r1-s1 17.4 r1-s2 17.4 r1-s3 17.4 r1-s4 17.4 r1-s5 17.4 r1-s6 17.4 r1-s7 17.4 r2 17.4 r2-s1 17.4 r2-s10 17.4 r2-s11 17.4 r2-s12 17.4 r2-s2 17.4 r2-s3 17.4 r2-s4 17.4 r2-s5 17.4 r2-s6 17.4 r2-s7 17.4 r2-s8 17.4 r2-s9 17.4 r3 17.4 r3-s1 17.4 r3-s2 17.4 r3-s3 17.4 r3-s4 18.1 18.1 r1 18.1 r2 18.1 r2-s1 18.1 r2-s2 18.1 r2-s4 18.1 r3 18.1 r3-s1 18.1 r3-s10 18.1 r3-s11 18.1 r3-s12 18.1 r3-s2 18.1 r3-s3 18.1 r3-s4 18.1 r3-s5 18.1 r3-s6 18.1 r3-s7 18.1 r3-s8 18.1 r3-s9 18.2 18.2 r1 18.2 r1-s2 18.2 r1-s3 18.2 r1-s4 18.2 r1-s5 18.2 r2 18.2 r2-s1 18.2 r2-s2 18.2 r2-s3 18.2 r2-s4 18.2 r2-s5 18.2 r2-s6 18.2 r2-s7 18.2 r3 18.2 r3-s1 18.2 r3-s2 18.2 r3-s3 18.2 r3-s4 18.2 r3-s5 18.2 r3-s6 18.2 r3-s7 18.3 18.3 r1 18.3 r1-s1 18.3 r1-s2 18.3 r1-s3 18.3 r1-s4 18.3 r1-s5 18.3 r1-s6 18.3 r2 18.3 r2-s1 18.3 r2-s2 18.3 r2-s3 18.3 r2-s4 18.3 r3 18.3 r3-s1 18.3 r3-s2 18.3 r3-s3 18.3 r3-s4 18.4 18.4 r1 18.4 r1-s1 18.4 r1-s2 18.4 r1-s3 18.4 r1-s4 18.4 r1-s5 18.4 r1-s6 18.4 r1-s7 18.4 r2 18.4 r2-s1 18.4 r2-s2 18.4 r2-s3 18.4 r2-s4 18.4 r2-s5 18.4 r2-s6 18.4 r2-s7 18.4 r3-s9 19.1 19.1 r1 19.1 r1-s1 19.1 r1-s2 19.1 r1-s3 19.1 r1-s4 19.1 r1-s5 19.1 r1-s6 19.1 r2 19.1 r2-s1 19.1 r2-s2 19.1 r3 19.1 r3-s1 19.1 r3-s2 19.1 r3-s3 19.1 r3-s4 19.1 r3-s5 19.2 19.2 r1 19.2 r1-s1 19.2 r1-s2 19.2 r1-s3 19.2 r1-s4 19.2 r1-s5 19.2 r1-s6 19.2 r2 19.2 r2-s1 19.2 r3 19.2 r3-s1 19.2 r3-s2 19.3 19.3 r1 19.3 r1-s1 19.3 r2 19.3 r2-s1 19.3 r2-s2 19.3 r2-s3 19.3 r2-s4 19.3 r2-s5 19.3 r3 19.3 r3-s1 19.3 r3-s2 19.4 19.4 r1 19.4 r1-s1 19.4 r1-s2 19.4 r1-s3 19.4 r2 19.4 r2-s1 19.4 r2-s2 19.4 r2-s3 19.4 r2-s4 19.4 r2-s5 19.4 r3 19.4 r3-s1 19.4 r3-s2 20.1 20.1 r1 20.1 r1-s1 20.1 r1-s2 20.1 r1-s3 20.1 r1-s4 20.1 r2 20.1 r2-s1 20.1 r2-s2 20.2 20.2 r1 20.2 r1-s1 20.2 r1-s2 20.2 r1-s3 20.2 r2 20.2 r2-s1 20.2 r2-s2 20.2 r2-s3 20.2 r3 20.3 20.3 r1 20.3 r1-s1 20.3 r2 20.3 r2-s1 20.4 20.4 r1 20.4 r1-s1 20.4 r2 20.4 r2-s1 21.1 21.1 r1 21.1 r1-s1

Vendor states this is fixed in 12.3R1 (unaffected)

Vendor states this is fixed in 15.1R1 (unaffected)

Affected range stops below 17.3R3-S12, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.4R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.1R3-S13, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.2R3-S8, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.3R3-S5, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.4R2-S8, 18.4R3-S9, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.1R3-S6, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.2R1-S7, 19.2R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.3R2-S6, 19.3R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 19.4R1-S4, 19.4R1-S4, 19.4R3-S3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.1R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.2R3-S1, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.3R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.4R3, so it looks safe — our inference, not a vendor statement

Affected range stops below 21.1R2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (2)

x_refsource_CONFIRMPatchVendor Advisory

Source: [email protected]

https://kb.juniper.net/JSA11246

x_refsource_MISCProductVendor Advisory

Source: [email protected]

https://www.juniper.net/documentation/us/en/software/junos/subscriber-mgmt-sessions/topics/topic-map/general-authentication-service-events-tracing.html

CVSS

7.5HIGH[email protected]

Attack Vector: NETWORK
Complexity: LOW
Privileges: NONE
User Interaction: NONE
Scope: UNCHANGED
Confidentiality: NONE
Integrity: NONE
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-772

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card