Vulnerability in Juniper Junos OS (CVE-2025-30650)
Summary
Vulnerability in Juniper Junos OS (CVE-2025-30650). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
A Missing Authentication for Critical Function vulnerability in command processing of Juniper Networks Junos OS allows a privileged local attacker to gain access to Linux-based line cards as root.
This issue affects systems running Junos OS using Linux-based line cards. Affected line cards include:
-
MPC7, MPC8, MPC9, MPC10, MPC11
-
LC2101, LC2103
-
LC480, LC4800, LC9600
-
MX304 (built-in FPC)
-
MX-SPC3
-
SRX5K-SPC3
-
EX9200-40XS
-
FPC3-PTX-U2, FPC3-PTX-U3
-
FPC3-SFF-PTX
-
LC1101, LC1102, LC1104, LC1105
This issue affects Junos OS:
- all versions before 22.4R3-S8,
- from 23.2 before 23.2R2-S6,
- from 23.4 before 23.4R2-S6,
- from 24.2 before 24.2R2-S3,
- from 24.4 before 24.4R2,
- from 25.2 before 25.2R2.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-30650 has been found in Juniper Junos OS.
Successful exploitation can lead to full system takeover. CVSS score: 6.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Juniper Junos OS CVE-2025-30650" on the vendor's site.
CVE-2025-30650 (Juniper Junos OS) — CWE-306 / CVSS v3 6.7
Attack vector: local / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in Juniper Junos OS.
Check the vendor advisory for the affected versions of Juniper Junos OS.
Severity: Medium (CVSS 6.7/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Juniper Junos OS を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory sirt@juniper.net
- patch sirt@juniper.net