CVE-2025-30656

Junos OS: MX Series, SRX Series: Processing of specific SIP INVITE messages by the SIP ALG will lead to an FPC crash

HIGH
7.5
CVSS Score
Published: April 9, 2025 at 08:01 PM UTC
Updated: June 17, 2026 at 09:09 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
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

An Improper Handling of Additional Special Element vulnerability in the Packet Forwarding Engine (PFE) of Juniper Networks Junos OS on MX Series with MS-MPC, MS-MIC and SPC3, and SRX Series, allows an unauthenticated, network-based attacker to cause a Denial-of-Service (DoS). If the SIP ALG processes specifically formatted SIP invites, a memory corruption will occur which will lead to a crash of the FPC processing these packets. Although the system will automatically recover with the restart of the FPC, subsequent SIP invites will cause the crash again and lead to a sustained DoS. This issue affects Junos OS on MX Series and SRX Series: * all versions before 21.2R3-S9, * 21.4 versions before 21.4R3-S10, * 22.2 versions before 22.2R3-S6, * 22.4 versions before 22.4R3-S5, * 23.2 versions before 23.2R2-S3, * 23.4 versions before 23.4R2-S3, * 24.2 versions before 24.2R1-S2, 24.2R2.

Affected

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

Affected range stops below 21.2R3-S9, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.4R3-S10, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.4R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.2R2-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.4R2-S3, so it looks safe — our inference, not a vendor statement
Affected range stops below 24.2R1-S2, 24.2R2, so it looks safe — our inference, not a vendor statement
juniper-mx10004 (environment) · juniper-mx10008 (environment) · juniper-mx2008 (environment) · juniper-mx2010 (environment) · juniper-mx2020 (environment) · juniper-mx204 (environment) · juniper-mx240 (environment) · juniper-mx304 (environment) · juniper-mx480 (environment) · juniper-mx960 (environment) · juniper-srx1500 (environment) · juniper-srx1600 (environment) · juniper-srx2300 (environment) · juniper-srx300 (environment) · juniper-srx320 (environment) · juniper-srx340 (environment) · juniper-srx345 (environment) · juniper-srx380 (environment) · juniper-srx4100 (environment) · juniper-srx4120 (environment) · juniper-srx4200 (environment) · juniper-srx4300 (environment) · juniper-srx4600 (environment) · juniper-srx4700 (environment) · juniper-srx5400 (environment) · juniper-srx5600 (environment) · juniper-srx5800 (environment)

Remediation

No guide yet

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

Patch and advisory references

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHjuniper
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-167

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.

Free plan, no card