Juniper Networks Session Smart Router
Session Smart Router, Session Smart Conductor, WAN Assurance Router: API Authentication Bypass vulnerability
Edge device · Router / network deviceknown edge product: Juniper Networks Session Smart Router Session Smart Router, (high confidence)
An Authentication Bypass Using an Alternate Path or Channel vulnerability in Juniper Networks Session Smart Router may allows a network-based attacker to bypass authentication and take administrative control of the device. This issue affects Session Smart Router: * from 5.6.7 before 5.6.17, * from 6.0 before 6.0.8 (affected from 6.0.8), * from 6.1 before 6.1.12-lts, * from 6.2 before 6.2.8-lts, * from 6.3 before 6.3.3-r2; This issue affects Session Smart Conductor: * from 5.6.7 before 5.6.17, * from 6.0 before 6.0.8 (affected from 6.0.8), * from 6.1 before 6.1.12-lts, * from 6.2 before 6.2.8-lts, * from 6.3 before 6.3.3-r2; This issue affects WAN Assurance Managed Routers: * from 5.6.7 before 5.6.17, * from 6.0 before 6.0.8 (affected from 6.0.8), * from 6.1 before 6.1.12-lts, * from 6.2 before 6.2.8-lts, * from 6.3 before 6.3.3-r2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5.6.7, < 5.6.17
- >= 6.1, < 6.1.12-lts
- >= 6.2, < 6.2.8-lts
- >= 6.3, < 6.3.3-r2
Fixed in 5.6.17, 6.0, 6.1.12-lts, 6.2.8-lts, 6.3.3-r2
- >= 5.6.7, < 5.6.17
- >= 6.1, < 6.1.12-lts
- >= 6.2, < 6.2.8-lts
- >= 6.3, < 6.3.3-r2
Fixed in 5.6.17, 6.0, 6.1.12-lts, 6.2.8-lts, 6.3.3-r2
- >= 5.6.7, < 5.6.17
- >= 6.1, < 6.1.12-lts
- >= 6.2, < 6.2.8-lts
- >= 6.3, < 6.3.3-r2
Fixed in 5.6.17, 6.0, 6.1.12-lts, 6.2.8-lts, 6.3.3-r2
Mitigation
The following software releases have been updated to resolve this issue: Session Smart Router: SSR-5.6.17, SSR-6.1.12-lts, SSR-6.2.8-lts, SSR-6.3.3-r2 and subsequent releases. It is suggested to upgrade all affected systems to one of these versions of software. In a Conductor-managed deployment, it is sufficient to upgrade only the Conductor nodes and the fix will be applied automatically to all connected routers. As practical, the routers should still be upgraded to a fixed version however they will not be vulnerable once they connect to an upgraded Conductor. Router patching can be confirmed once the router reaches the “running" (on 6.2 and earlier) or “synchronized” (on 6.3+) state on the Conductor". This vulnerability has been patched automatically on devices that operate with WAN Assurance (where configuration is also managed) connected to the Mist Cloud. As practical, the routers should still be upgraded to a version containing the fix. It is important to note that when the fix is applied automatically on routers managed by a Conductor or on WAN assurance, it will have no impact on data-plane functions of the router. The application of the fix is non-disruptive to production traffic. There may be a momentary downtime (less than 30 seconds) to the web-based management and APIs.
Workaround
There are no known workarounds for this issue.
References
- Vendor advisory supportportal.juniper.net
- Vendor advisory kb.juniper.net/JSA94663
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.