{ "dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": { "cveId": "CVE-2025-21589", "assignerOrgId": "8cbe9d5a-a066-4c94-8978-4b15efeae968", "state": "PUBLISHED", "assignerShortName": "juniper", "dateReserved": "2024-12-26T14:47:11.667Z", "datePublished": "2026-01-27T20:32:13.334Z", "dateUpdated": "2026-01-27T21:28:02.560Z" }, "containers": { "cna": { "affected": [ { "defaultStatus": "unaffected", "product": "Session Smart Router", "vendor": "Juniper Networks", "versions": [ { "lessThan": "5.6.17", "status": "affected", "version": "5.6.7", "versionType": "semver" }, { "changes": [ { "at": "6.0.8", "status": "affected" } ], "lessThan": "6.0.8", "status": "unaffected", "version": "6.0", "versionType": "semver" }, { "lessThan": "6.1.12-lts", "status": "affected", "version": "6.1", "versionType": "semver" }, { "lessThan": "6.2.8-lts", "status": "affected", "version": "6.2", "versionType": "semver" }, { "lessThan": "6.3.3-r2", "status": "affected", "version": "6.3", "versionType": "semver" } ] }, { "defaultStatus": "unaffected", "product": "Session Smart Conductor", "vendor": "Juniper Networks", "versions": [ { "lessThan": "5.6.17", "status": "affected", "version": "5.6.7", "versionType": "semver" }, { "changes": [ { "at": "6.0.8", "status": "affected" } ], "lessThan": "6.0.8", "status": "unaffected", "version": "6.0", "versionType": "semver" }, { "lessThan": "6.1.12-lts", "status": "affected", "version": "6.1", "versionType": "semver" }, { "lessThan": "6.2.8-lts", "status": "affected", "version": "6.2", "versionType": "semver" }, { "lessThan": "6.3.3-r2", "status": "affected", "version": "6.3", "versionType": "semver" } ] }, { "defaultStatus": "unaffected", "product": "WAN Assurance Managed Router", "vendor": "Juniper Networks", "versions": [ { "lessThan": "5.6.17", "status": "affected", "version": "5.6.7", "versionType": "semver" }, { "changes": [ { "at": "6.0.8", "status": "affected" } ], "lessThan": "6.0.8", "status": "unaffected", "version": "6.0", "versionType": "semver" }, { "lessThan": "6.1.12-lts", "status": "affected", "version": "6.1", "versionType": "semver" }, { "lessThan": "6.2.8-lts", "status": "affected", "version": "6.2", "versionType": "semver" }, { "lessThan": "6.3.3-r2", "status": "affected", "version": "6.3", "versionType": "semver" } ] } ], "datePublic": "2025-02-04T17:00:00.000Z", "descriptions": [ { "lang": "en", "supportingMedia": [ { "base64": false, "type": "text/html", "value": "
An Authentication Bypass Using an\nAlternate Path or Channel vulnerability in Juniper Networks Session Smart\nRouter may allows a network-based attacker to bypass authentication\nand take administrative control of the device.
This issue affects Session Smart Router:
This issue affects Session Smart Conductor:
This issue affects WAN Assurance Managed Routers:
The following software releases have\nbeen updated to resolve this issue:
\n\n
\nSession Smart Router: SSR-5.6.17, SSR-6.1.12-lts, SSR-6.2.8-lts,\nSSR-6.3.3-r2 and subsequent releases.
\nIt is suggested to upgrade all affected systems to one of these versions of\nsoftware. In a Conductor-managed deployment, it is sufficient to upgrade only the\nConductor nodes and the fix will be applied automatically to all connected\nrouters. As practical, the routers should still be upgraded to a fixed version\nhowever 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\".
\n
This vulnerability has been patched\nautomatically on devices that operate with WAN Assurance (where configuration is also managed) connected\nto the Mist Cloud. As practical, the routers should still be upgraded to a version\ncontaining the fix.
\n
\nIt is important to note that when the fix is applied automatically on routers managed\nby a Conductor or on WAN assurance, it will have no impact on data-plane\nfunctions of the router. The application of the fix is non-disruptive to\nproduction traffic. There may be a momentary downtime (less than 30 seconds) to\nthe web-based management and APIs.